Search Issue Tracker
By Design
Votes
4
Found in
2018.3.0a1
2018.3.6f1
2019.1.0a1
2019.2.0a1
Issue ID
1131604
Regression
Yes
ScriptedImporter Shader.Find returns null the first time the project is opened
How to reproduce:
1. Download the user-submitted project ("ScriptedImporterShaderTest.zip")
2. Make sure that it doesn't already have a generated Library folder and open the project
3. Observe the Console Window
Expected result: The Shader is successfully found without any errors in the console
Actual result: Shader.Find returns the "shader" object as null
Reproduced in: 2019.2.0a7, 2019.1.0b5, 2018.3.7f1
Not reproducible in: 2017.4.22f1
Note: Reimporting the asset 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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (2019.2.X):
This has never been intended to work since finding shaders by name bypasses dependency checking