Search Issue Tracker
By Design
Votes
0
Found in
2020.1
2020.2
2020.2.2f1
2021.1
2021.2
Issue ID
1309875
Regression
Yes
AssetDatabase.LoadAssetAtPath returns null when called after AssetDatabase.ImportAsset inside OnImportAsset method
Reproduction steps:
1. Open the user's attached project
2. Select Custom Shaders/Test asset and reimport it
3. Observe the Inspector windows
Expected result: Compiled Shader is Hidden/Compiled
Actual result: Compiled Shader is empty
Reproducible with: 2020.1.0b16, 2020.1.17f1, 2020.2.3f1, 2021.1.0b5, 2021.2.0a4
Not reproducible with: 2019.4.20f1, 2020.1.0b13
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
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
Resolution Note:
Creating an asset in the middle of an import, and trying to import it, is not allowed by the AssetDatabase as it might cause infinite import loop or performance implications. More information about batching with the Asset Database can be found here: https://docs.unity3d.com/Manual/AssetDatabaseBatching.html