Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.15f1
Issue ID
UUM-40531
Regression
No
[Android] URP shader link error occurs when Player runs on Samsung Note 4
Reproduction steps:
1. Open the attached project “URPProject”
2. Build the Project and Run it on Android
3. Observe the screen on the device when the app launches
Expected result: A sofa and Google image are visible on the screen
Actual result: A black screen is rendered
Reproducible with 2021.3.15f1 according to the User
Not Reproducible with these devices:
VLNQA00518 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 12
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00278 - Xiaomi Redmi Note 7 (Redmi Note 7), CPU: Snapdragon 660, GPU: Adreno 512, OS: 9.0.0
VLNQA00139 - Vivo Xplay6 (vivo Xplay6), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 7.1.1
VLNQA00132 - Xiaomi Mi 5s (MI 5s), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 6.0.1
Reproducible with this device(User):
Samsung Galaxy Note 4 (Adreno 420)
Tested with: Intel macOS 13.3.1
Note: Error found in the Android logcat provided by the user:
04-26 17:19:08.820 25834-25964/? E/Unity: -------- Shader Universal Render Pipeline/DH/Lit
-------- GLSL link failed, no info log provided.
04-26 17:19:08.820 25834-25964/? D/Unity: Note: Creation of internal variant of shader 'Universal Render Pipeline/DH/Lit' failed.
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
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
- Root motion is not reapplied when transitioning from an animation without root motion to an animation with root motion
- Crash on Walk when opening a specific project
- [WebGL] Unclear error when GZIP compressed data or WebAssembly don't have correct HTTP headers
Resolution Note:
Thank you for your bug report.
After reviewing the issue, there's not enough information to be able to properly process the case. The logs point to a linker error in a custom shader Shader Universal Render Pipeline/DH/Lit, however this shader is not in the project for us to review.
The case will now be closed, please contact your account manager or PRM if you’d like to discuss this specific case in more detail and provide more information.