Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.9f1
2022.1.15f1
2022.2.0b7
2023.1.0a9
2023.2.0a1
Issue ID
UUM-13509
Regression
No
AssetDatabase is not ready in InitializeOnLoadMethod nor in OnPostProcessAllAssets when the Library is imported after deleting it
Reproduction steps:
1. Before opening the user’s attached project make sure the Library folder is deleted
2. Open the user’s attached project
3. Observe the Console window
Expected result: All “xyzzy” messages indicate that all resources have been loaded
Actual result: Some “xyzzy” messages indicate that not all resources have been loaded
Reproducible with: 2021.3.9f1, 2022.1.14f1, 2022.2.0b6, 2023.1.0a8
Couldn’t test with: 2020.3.39f1 - Errors in packages scripts
Reproducible on: macOS 12.5
Note: Resources only fail to load when the Library folder is not present and reimported on load
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
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.
Resolution Note (2023.2.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.