Build error: "Shader compiler: internal error compiling shader snippet type=0 platform=5"

Build failed often on Unity Cloud Build with the following errors:

Often failed, and sometimes succeeded.

On Editor, alway succeeded.

Are there any solutions?

 

Same problem today, but with 'Legacy Shaders/VertexLit' shader. Did you find solutuin?

 

We are seeing a similar error with our iOS Unity Cloud Build.

3043: [Unity] Shader compiler: internal error compiling shader snippet type=0 platform=14: Protocol error - failed to read correct magic number
3044: [Unity] UnityEditor.BuildPipeline:BuildPlayerInternalNoCheck(String[], String, BuildTarget, BuildOptions, Boolean, UInt32&)
3045: [Unity] UnityEditor.CloudBuild.Builder:Build()
3046: [Unity] Shader compiler: UnityShaderCompiler compiler executable disappeared on thread 1915822848, restarting

We don't have any custom shaders and initiating a "Clean Build All" sometimes results in a successful build. We are running Unity 5.3.3f1. Has this been resolved in later versions?

 

Any news on this? We have a project that has the same error. Builds most of the time on Android, but fails most of the time on Android.
Always works when building from Editor.

 

I can't state this as a definitive answer, but I was having the same issues after Updating to Unity 5.3.4b19.
I found that everywhere I had the Material 'Sprites-Default'. It had been removed and replaced by nothing in the Sprite Renderers. And If I used that material in a Particle it showed this caption where the material should have been 'Hidden/InternalErrorShader.

So you don't really need any custom shaders for this kind of thing to occur in my experience.

 

@Ryanc_unity ,

I would be willing to share my project with you in order to get this fixed.
Is there any other way to get my project to you besides cloud build?

Sorry for the inconvenience.

 

@Ryanc_unity
Having the same issue here. First we used a legacy shader on the player and started cloud build. The Android target went through nicely, however the iOS target failed. I tried building for iOS locally and everything was good.

So I switched the shader to "Mobile/Bumped Specular", pushed waited.. and then the iOS build worked. However the Android target failed So just the other way around..

I'll send you a link to the cloud build project in a moment. I hope you guys can figure something out.

And for completeness: we are using version 5.4.0f3

 

@Ryanc_unity I also seem to be experiencing this issue with both iOS and Android

EDIT: I just retried building with no changes and now it works...

 

Same issue. Repro:

1. Had cloud build set up with Unity 5.3.4f1, target Android. Everything worked.
2. Switched to Unity 5.4.0f1. Updated project settings and pushed. Updated cloud build settings for the branch to use
   5.3.4f1.
3. Started build. Result: Failure.

Here's log:
56: [Unity] Shader compiler: internal error compiling shader snippet type=0 platform=5: Protocol error - failed to read correct magic number
57: [Unity] Shader error in 'Sprites/Default': Internal error communicating with the shader compiler process
58: [Unity] Player export failed. Reason: Shader error in 'Sprites/Default': Internal error communicating with the shader compiler process
59: ! build of 'develop-android' failed. compile failed

 

starting to see this error in my android cloud build now too, in addition to the ios build. really weird. seems to be random as my builds were working fine up until a few days ago and I didnt really make any real changes

 

This is somewhat non-deterministic. In my case, restarting a build often results in a successful build.

 

Making a new build configuration might be a work around.

I've consistently been experiencing this error in 8 out of my last 9 builds for both iOS and Android on Cloud Build - but not locally.
Now I simple renamed my build configuration in Cloud Build, made a copy of it and gave the copy a new name - and now it builds. Library Cache is disabled for my project but the error was still consistent.

@Unity: Let me now if I somehow can be helpful tracking this bug down by providing build logs, build configurations or anything. I would be happy to help as this bug is really really annoying.

/Martin

 

@Unity We are also seeing this issue pretty regularly in our builds, let us know if you need anything to help debug.

 

I'm seeing this in Unity Cloud builds (but not local builds) after attempting to upgrade from 3.5.5f1 to 5.4.x.

 

lot's of shader compiltion errors lately

Cloud both 5.4.1 and 5.4.2
both iOS and Android

it was workign perfecly until a few days a go

 

Same here. In this past week, >75% of our Android/iOS builds (Unity 5.4.2f2) with no library cache failed with this error, and a small percentage of Android/iOS builds with library cache. It appears to be entirely independent of the actual shader being compiled, we've tried replacing complicated shaders with simple ones, moved shaders to Resources folder and back and even removed shaders only for building to fail on the next shader in the list.
This is a huge issue within our build process.

 

iOS: still getting shader compilation error 100% of the time, I am unable to get any build on the cloud.

Android, build failing 100% of the time, shader error disappeared today but got another error without any explanation.

Both iOS and Android builds are working locally.

 

We've been trying all day to get a build out to our testers, and it keeps failing. I really hope you guys have something up your sleeves - this is severely affecting our productivity. :/

 

Plus one for this error!

[Unity] Player export failed. Reason: Shader error in 'Hidden/Unlit/Transparent Colored 2': Internal error communicating with the shader compiler process

 

Also have this error occurring in something like 25% of our builds. Another 25% are errors during pull from our mercurial repository on bitbucket.

We can still use Cloud Build since building again 1-2 times usually results in a successful build, but It would be nice if Cloud Build only failed if there is an actual error in the project.

 

The issue still persists. It fails about once per 10 builds.

 

Getting these as well now

 

Project one from Cloud iOS Build give this:

Project two from Cloud iOS Build give this:

 

Seems to still be happening:

[Unity] Shader compiler: internal error compiling shader snippet type=0 platform=5: Protocol error - failed to read correct magic number
907: [Unity] Shader error in 'Particles/Additive': Internal error communicating with the shader compiler process

Unity 5.5 UCB

- But only for the first build. 2nd build runs successfully.

 

Shader compiler: internal error disassembling shader snippet type=16 platform=4: Protocol error - failed to read correct magic number on 5.4.4f1

Failing all the time, currently blocked

 

Got the same error today

http://i.imgur.com/ADzAsIA.png

I would really much like to know what the status on this, because relaunching the build manually and hoping it's going to work ... for a premium service it's not acceptable.

 

Hello,

As mentioned in the Known Issues thread:

So you should be seeing the errors very infrequently.

I hope this helps.

- Sophia

 

Happened to me today after changing unity target build from 5.5.0f3 to unity 5.5.2f1

 

Having the seem issue today.

36146: [Unity] Shader error in 'Particles/Alpha Blended': Internal error communicating with the shader compiler process
36136: [Unity] Shader compiler: internal error compiling shader snippet type=0 platform=5: Protocol error - failed to read correct magic number

 

Unity] Shader compiler: internal error compiling shader snippet type=0 platform=5: Protocol error - failed to read correct magic number
[Unity] Shader error in 'Sprites/Default': Internal error communicating with the shader compiler process

today(

 

Got this today:
1080: [Unity] Player export failed. Reason: Shader error in 'Standard': Internal error communicating with the shader compiler process

 

Me too

280: [Unity] Shader compiler: internal error compiling shader snippet type=0 platform=5: Protocol error - failed to read correct magic number
281: [Unity] Shader error in 'Sprites/Default': Internal error communicating with the shader compiler process
282: [Unity] Player export failed. Reason: Shader error in 'Sprites/Default': Internal error communicating with the shader compiler process

After as load of
PVRTC texture format is not supported, decompressing texture

 

@SophiaC will this ever be fixed? This has been a problem for us for more than half a year now. The cloud build is useless when it cannot be relied on and we are paying for this service. 3 of 4 build attempts fail.

 

Thanks for your reply.

Average build fail rate (not success rate) is 64% for us the last three months, caused by internal shader compiler error. It should be fairly easy for your team to spot which project build configurations have exactly this kind of problem and improve the build process from there? I do not understand why this has taken so long. Anyway, let's see after Thursday...

 

..and the problem persists.

 

Hi guys,

I'm having this an awful lot since upgrading to 5.6, more than 50% easily.

Project name is PuzzlerNameGame, it's causing me a lot of headaches. I'm also having a lot of complaints about .meta files that shouldn't exist (for files I've removed), but I don't have those in my local builds. I've tried clean builds too.

 

I got the same problem ,unity version is 5.5.3f1

 

I just add the these shaders to always include group,and no compile errors when use ucloud build .But I do not think this is the right way to solve this issue.

 

Please do not add the Standard Shader to the Always Included list, though! I don't know if you have done that but I'm just putting that out there for anyone who might see

 

Thanks for replay . But If I don't put these shaders to always include , When UCloud build ,it will show me the compile error "Shader compiler: internal error compiling shader snippet type=0 platform=5: Protocol error - failed to read correct magic number" ,and I don't know how to fix these . These shaders I build without UCloud gets no this error ...

Thanks ~

 

Hi @fisher-lv, please see Phil's post about the Shader compiler

 

Hey, any update on how to fix? I started getting these errors few days ago and now I am unable to build it via cloud anymore (build via editor works fine).

Thanks!

 

Same here, started gettings these errors one day ago. First I though it's my problem, but no. In editor everything is fine.



Error example:

Code (CSharp):

1. 211: [Unity] Shader compiler: internal error compiling shader snippet type=0 platform=5: Protocol error - failed to read correct magic number
2. 212: [Unity] Shader error in 'Sprites/Default': Internal error communicating with the shader compiler process
3. 213: [Unity] UnityEngine.Debug:LogWarning(Object)
4. 214: [Unity] Player export failed. Reason: Shader error in 'Sprites/Default': Internal error communicating with the shader compiler process
5. 215: ! build of 'ios-development' failed. compile failed
6. 216: publishing finished successfully.
7. 217: Finished: FAILURE

 

I find that this occurs almost 100% after I build without caching the library.
After I get this error, I switch back to caching and it builds fine.

 

even with caching it can occur.
but with caching it's (obviously) less frequent; because there is less things to build.

 

Experiencing this 100% of the time after adding in a particle system to the project yesterday. Trace:

5799: [Unity] *** Completed 'Build.Player.AndroidPlayer' in 116 seconds (116373 ms)
5800: [Unity] Player export failed. Reason: Shader error in 'Mobile/Particles/Alpha Blended': Internal error communicating with the shader compiler process
5801: [Unity] UnityEngine.DebugLogHandler:Internal_Log(LogType, String, Object)
5802: [Unity] UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
5803: [Unity] UnityEngine.Logger:Log(LogType, Object)
5804: [Unity] UnityEngine.Debug:Log(Object)
5805: [Unity] UnityEditor.CloudBuild.BuildLogger:Log(String, Object[])
5806: [Unity] UnityEditor.CloudBuild.Builder:Build()
5807: [Unity] Refresh: detecting if any assets need to be imported or removed ... Refresh: elapses 0.030030 seconds (Nothing changed)
5808: [Unity] Refresh: detecting if any assets need to be imported or removed ... Refresh: elapses 0.028994 seconds (Nothing changed)
5809: [Unity] Cleanup mono
5810: [Unity] Checking for leaked weakptr:
5811: [Unity] Found no leaked weakptrs.
5812: [Unity] Assertion failed on expression: 'ms_Instance != NULL'
5813: [Unity] ##unity-automation:{"messageType":"MemoryLeaks","allocatedMemory":752911,"memoryLabels":[{"Default":96},{"Permanent":16128},{"Thread":616},{"Manager":1976},{"GfxDevice":19800},{"GfxThread":2688},{"Physics":8},{"Serialization":12704},{"JobScheduler":144},{"GarbageCollector":1048576},{"Renderer":224},{"Terrain":224},{"STL":131584},{"String":56826},{"DynamicArray":3112},{"Utility":-1048576},{"PoolAlloc":-224},{"ScriptManager":3280},{"Sprites":482944},{"VR":11400},{"EditorUtility":544},{"AssetImporter":1056},{"RestService":64},{"License":965},{"UnityConnect":6024},{"Collab":728}]}
5814: ! Unity player export failed!
5815: ! build of 'android' failed. compile failed
5816: Publishing build 27 of viker-limited/stoppr for target 'android'...
5817: publishing finished successfully.
5818: Storing CACHE_PATH to cache key library_latest5
5819: done.
5820: Build step 'Execute shell' marked build as failure
5821: postbuildstatus finished successfully.
5822: Finished: FAILURE

Haven't managed to resolve yet. Will keep trying.