Search Issue Tracker
Won't Fix
Votes
3
Found in
2017.1.2f1
Issue ID
971601
Regression
No
AssetDataBase.FindAssets fails to find changed scriptable objects by type
Steps to reproduce:
1. Open user attached project
2. Observe that a Locale extends a Scriptable Object
3. type "t:Locale" within the project window search bar
4. Notice that the asset does not appear
Actual result: The name Locale appears to be condemned
Expected result: "t:Locale" shoud return assets of type Locale
Reproduced in: 2018.1.0a5, 2017.3.0b11, 2017.2.0p3, 2017.1.2p3, 5.6.4p3, 5.5.5p2
Comments (1)
-
Noisecrime
Jan 25, 2020 15:32
Quick note for those who may run into Unity search or use of AssetDatabase.FindAssets() failing to find a scriptableObject.
This may be due to a bug ( unsure if its the exact one addressed by this issue as it is not explicitly defined in the report above ) where changing the namespace ( or maybe even the name of the scriptableObject script file ) will cuase Unity to fail to find the asset.
The current workaround to fix the issue is to select the asset and reimport it. This process could be automated with an editor script.
more information - https://forum.unity.com/threads/assetdatabase-findassets-not-working.587062/
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 (2019.1.X):
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.