Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
1
Found in
2020.3.35f1
2021.2.19f1
2022.1.3f1
2022.2.0a11
Issue ID
UUM-2634
Regression
No
Assets dependencies load in the wrong order resulting in "None" being referenced
Reproduction steps:
1. Open attached project "Reference.zip"
2. In Project window, select Assets/Content/MTFLocalizationManager.asset
3. In Inspector window, observe Startup Sources dropdown
4. If there aren't any missing references, restart the editor and repeat the steps
Expected result: No references are missing
Actual result: Many of the references are missing
Reproducible with: 2019.4.12f1
Could not test with: 2018.4.28f1, 2020.1.8f1, 2020.2.0b6 (console errors break project)
Workarounds:
1. Reloading the asset fixes the problem.
2. Wrapping the contents of the function in an EditorApplication.delayCall fixes the problem.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2022.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.