Search Issue Tracker
By Design
Votes
2
Found in
2021.2.0a1
2021.2.0b11
2022.1
Issue ID
1365562
Regression
Yes
[macOS] [Mobile] Shader compilation is failed due to Invalid Bytecode error when building with macOS Editor
How to reproduce:
1. Open the attached project "MacShaderCompilationIssue-2021.2.zip"
2. Open Build Settings and change to Android platform
3. In the Build Settings, press Build And Run
Expected result: The leaves on the tree are not displayed as image boxes
Actual result: The leaves on the tree are shown as image boxes
Reproducible with (Bytecode errors appear and shaders compiling fails): 2021.2.0a1, 2021.2.0b13, 2022.1.0a10
Not reproducible with (Bytecode errors appear and shaders compile successfully): 2021.1.0a10, 2021.1.22f1
Could not test with: 2019.4.30f1, 2020.3.19f1, 2021.1.0a9 (shader errors)
Note:
- Does not reproduce with Windows version of Editor
- Only reproduces when building for Android or iOS platform
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
- Diagnostics logs are missing, duplicated, or out of order when viewing Player sessions in Cloud Diagnostics
- Prefab Overrides “Apply” button is too big and overlaps with the context menu’s outline
- Prefab Overrides “No Overrides” text is too large, and the the Context Menu of the Parent GameObject has a lot of empty space when opened
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
Resolution Note (2022.1.X):
The root cause was in the shader code itself.