Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.27f1
Issue ID
UUM-40827
Regression
Yes
Generated classes are not found when using TypeCache
Reproduction steps:
1. Open the attached “ASDQWE” project
2. In the top menu select Tools > Get Marked Classes
3. Observe the Console Window
Expected result: “Found 1 marked classes” and “Found 1 factory classes” logs are displayed
Actual result: “Found 1 marked classes” and “Found 0 factory classes” logs are displayed
Reproducible with: 2021.3.27f1, 2022.2.0a11
Not reproducible with: 2022.3.2f1, 2023.1.0f1, 2023.2.0a19
Fixed in: 2022.2.0a12
Reproducible on: Intel MacOS 13.4
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
- Long Property names are not truncated in the Add Property dropdown in the Animation window when the Long Property name does not fit
- [iOS] High CPU load when device keyboard is open
- Selected Animation clip in the Animation window changes when the Domain Reload is triggered
- Animation window scrollbar keeps resetting when the scrollbar width is changed after adding an event
- LocalizationSettings.InitializationOperation hangs when re-entering Play Mode with Domain Reload disabled
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Fixed behavior can be found on newer Unity versions, starting 2022.2.a12
Resolution Note (2021.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Fixed behavior can be found on newer Unity versions, starting 2022.2.a12