Search Issue Tracker
Won't Fix
Votes
1
Found in
2022.3.15f1
Issue ID
UUM-59686
Regression
No
"GetMainAssetTypeAtPath" and "GetMainAssetTypeFromGUID" functions return the wrong type when the same type name exists in another namespace
Reproduction steps:
1. Open the attached “BugRepro” project
2. Run the test (Test > Find MyMaterial assets)
3. Observe the Console window
Expected result: No warnings are printed out
Actual result: Warnings are printed out regarding retrieved asset types not matching the real asset types
Reproducible with: 2022.3.15f1, 2023.1.8f1
Not reproducible with: 2023.2.0b1, 2023.2.3f1, 2023.3.0a17
Couldn’t test with: 2021.3.33f1, 2023.2.0a1 - 2023.2.0a22 - No support for the “AssetDatabase.GetMainAssetTypeFromGUID” function
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Note:
- If the Library folder does not exist, launch the project, then close it and re-open it again. Otherwise, the bug does not reproduce.
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
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.