Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.2
2021.2.5f1
2022.1
2022.2
Issue ID
1387706
Regression
Yes
Project gets stuck on import loop when upgrading to newer streams
Reproduction steps:
1. Open user's attached project
Expected result: Project opens
Actual result: Project gets stuck on import loop (stuck on compiling C# scripts and reloading script assemblies)
Reproducible with: 2021.2.0a6, 2021.2.11f1, 2022.1.0b7, 2022.2.0a3
Not reproducible with: 2019.4.35f1, 2020.3.27f1
Could not test with: 2021.2.0a1 - 2021.2.0a5 due to Unity Test Framework package errors: error CS1061: 'BuildPlayerOptions' does not contain a definition for 'subtarget' and no accessible extension method 'subtarget' accepting a first argument of type 'BuildPlayerOptions' could be found (are you missing a using directive or an assembly reference?) etc.
Note: Might have regressed between 2021.2.0a1 - 2021.2.0a5
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Warnings when warming up shaders with GraphicsStateCollection
- Color and Location fields disappear when removing gradient marker in the HDR gradient Editor (linear) window
- Create Node window appears on the top left corner of the Editor when opening window with space keyboard shortcut after selecting a Context
- HasCharacters() returns false when checking Emojis using surrogate pairs, despite characters being present in the Font Asset
- An error is thrown when building AssetBundles with DisableWriteTypeTree and StripUnityVersion flags
Resolution Note:
The project contains a script under Packages/com.vrchat.vrcsdk3 (Editor\UPMImporter\UPMImporter.cs) that is causing the endless loop. Rather than adding project dependencies with a script in the custom package, that package's package.json file should include a "dependencies" property with those dependencies so that the Package Manager can resolve them as part of the project initialization and avoid any kind of endless loop like this. Also, in 2019.3 and newer, the "com.unity.package-manager-ui" package no longer exists as a package; its code has been merged into the main Unity Editor codebase, so there is no need to add it as a dependency anymore.