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
- [Hub][Linux] Hub .AppImage does not allow to upgrade the Hub from 2.4.5 to 3.0.0-beta.2
- [Profiler] Current frame button initially hides profile frame marker
- Missing function to reset or unset a specific resource in the local binding space of compute shaders
- [Linux][Hub] Unity Hub 2.4.5 does not open "Add modules" window when clicking "Install with Unity Hub" in Build Settings
- Multiple errors appear in the Console when building for IL2CPP
Resolution Note (2019.2.X):
This has never been intended to work since finding shaders by name bypasses dependency checking