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
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
- [RenderingDebugger][InputSystemPackage] Ctrl+Backspace shortcut doesn't work to open the Rendering Debugger when New Input System is in use
Resolution Note (2019.2.X):
This has never been intended to work since finding shaders by name bypasses dependency checking