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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2019.2.X):
This has never been intended to work since finding shaders by name bypasses dependency checking