Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.3.0a1
2019.3.0b1
2020.1.0a1
Issue ID
1179661
Regression
No
AssetDatabase.FindAssets("t:type") does not find scriptable objects when the referenced script is renamed
How to reproduce:
1. Open the attached project ("case_1179661-Asset_Database_Version_2_Issue.zip")
2. Select Issue Demo/Find Animal Assets from Menu
3. Notice in the console that 3 assets were found
4. Change the name of "Animal.cs" script and change the class name accordingly inside the script
5. Change line 9 of "FindAnimalAsset.cs" to reflect the changes from step 4
6 Select Issue Demo/Find Animal Assets from Menu
7. Inspect the console
Expected results: 3 assets are found
Actual results: No assets are found
Reproducible with: 2017.4.32f1, 2018.4.8f1, 2019.2.4f1, 2019.3.0.0b1, 2020.1.0a2
Notes:
1. This issue reproduces on both Version 1 and Version 2 of Asset Pipeline modes
2. Reimporting the scriptable objects which have the reference to the renamed script fixes the issue
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
- "Initialization Mode" and "Update Mode" drop-downs are not localized in the Custom Render Texture asset
- Switching Graphics Default or DevLook Profile to “NightSkyRenderingSettings Profile” throws “KeyNotFoundException” error in the Console window
- Section separator renders in the wrong place in Search Journaling and Archetypes windows
- [D3D12][UWP] Additional persistent shadows are drawn in UWP builds when using D3D12
- Search Journaling window link to Journal Manager documentation isn’t working
Resolution Note:
Due to low severity we're not fixing this issue. If you believe this case is an important bug, please respond and we'll take a look again