Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.36f1
2022.3.22f1
2023.2.15f1
6000.0.0b12
7000.0.0a1
Issue ID
UUM-66864
Regression
No
Not all assemblies are found in the current AppDomain when scanning with TypeCache
How to reproduce:
1. Open the attached project “TypeCache_Missing_Assemblies_Report.zip“
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Scan assemblies (BUG > Reproduce TypeCashe bug)
Expected result: “TypeCache was missing types from 0 assemblies.“ is logged in the Console
Actual result: “TypeCache was missing types from 24 assemblies.“ is logged in the Console
Reproducible with: 2021.3.36f1, 2022.3.22f1, 2023.2.15f1, 6000.0.0b12
Reproducible on: macOS 14.4 Sonoma (Intel)
Not reproducible on: No other environment tested
Note: Different amount of assemblies are missing on different streams - 2021.3.36f1 (24), 2022.3.22f1 (21), 2023.2.15f1 (22), 6000.0.0b12 (25)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
TypeCache is missing assemblies found in current AppDomain is due to no managed types present in the assembly or it being optimized out of TypeCache due to having a Unity specific counterpart.
Overall querying for object derivatives is not an intended use case for TypeCache.