Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2018.4
2018.4.12f1
2019.2
2019.3
2020.1
Issue ID
1196265
Regression
No
Unity doesn't recognize some assemblies resulting in missing components
Reproduction steps:
1. Open "PackageLoadFailure_2018412.zip" project
2. Select "StyleTestPrefab" GameObject
3. Notice "StyleSheets" component
4. "Reimport All"
5. Select "StyleTestPrefab" GameObject
Expected Result: Components from Packages are not missing
Actual Result: Missing Components from Packages
Reproduced with: 2020.1.0a12, 2019.3.0b10, 2019.2.12f1, 2018.4.12f1
Did not reproduce on: 2017.4.34f1
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
- Adaptive Performance Samples are using the obsolete "FindFirstObjectByType" method
- [UVCS] Wrong folder moved to changelist after shelve/unshelve sequence
- Object Selector becomes unresponsive when selecting root UI Document as Data Source for Add Binding in UI Builder
- Search #Light.m_Shadows.m_Type query block does not detect default Light objects in Scene unless they were modified
- Shader Graph "Create Node" menu has a doubled text in search when the text was deleted replaced to the space and then the exact same text was entered
Resolution Note (2020.1.X):
Fixing this issue requires implementing new features and has been postponed.
The workaround for this issue is to put all managed .dlls that have dependencies between themselves into the same folder.