Unknown shader compiler error using Unity 2019.2.8f1 when building iOS

Hi I encountered shader compiler error using Unity 2019.2.8f1 when building iOS app in MacOS Catalina.

Here's the error log:


However, when I tried building using Unity 2018.4.10f1, everything just works. Is it a bug in Unity 2019 or there're new changes that cause this error?

p/s: I'm using custom shader and built-in shader such as standard and mobile shaders

 

I have same issue.
2019.2.6 on macOS Mojave works correctly. 2019.2.8 on macOS Catalina has same issue.

I don't use home made shader, I'm using only post processing stack and shaders in standard assets.

 

Same issue, with Unity 2019.2.8f1 on Catalina, when building to Android....

 

As minimal as it can get, just a blank new project only with TextMesh Pro essential resources package imported.
Issue ID: 1190831

 

On a side note I've just tested with 2019.3.0b6 and everything seems to be working fine, so it must be something on the 2019.2.x branch.

 

Same issue with 2019.2.8f1..., any updates?

 

As I posted above, Unity 2019.3.0b6 is working correctly with the same setup & project.

So, I've tried replacing UnityShaderCompiler with the one from b6 and guess what, everything seems to be working now. Tested this with 2019.2.8f1 & 2019.2.9f1

For now, that'll be enough for me to keep working while Unity provides an official fix...

 

How you replace UnityShaderCompiler? Where its location? Ths

 

It's at Applications/Unity/Hub/Editor/2019.2.9f1/Unity/Contents/Tools/UnityShaderCompiler

 

Same issue here. Can also confirm it works with 2019.3 but not any of 2019.2.7f2, 2019.2.8f1, 2019.2.9f1. Works fine on Mojave, but not on Catalina.

 

I have Unity 2019.2.9f1 and Catalina 10.15 beta
This problem with shaders is very strange. My first attempt to build my project failed with ~72 shader compiler errors. I didn't change anything and just pressed the build button again. Only two errors remain. I made a third attempt - all error gone...

However I still have "shader unsupported" errors on my iOS device.

 

Same issue here.

 

@AytoMaximo Yeah, building again goes through, but the app doesn't run on the device, with lots of missing/unsupported shader errors.

 

I have same issue with unity 2019.2.9f1 and macOS Catalia 10.15.

 

same issue here. 2019.2.9f1 on Catalina 10.15. No errors in my project at all, but when compiling after 20 seconds 300 errors with these shader errors pop up. Friend manages to build without problem on his Windows PC. Build always succeeds and builds in xcode without issues.

When launching on iPhone XS iOS 13.1 its all pink.

It appears this error is relatively new since everyone just reported it through the forums the past week, all with the same platform, same version OS. Guess we'll have to wait for a dev to respond.

 

Same here (tvOS also). I've replaced UnityShaderCompiler with the UnityShaderCompiler from 2019.3.0b7 and it helps. PixelEnvision thanks for the tip. Hope will be fixed soon.

 

Can confirm, this works. The only solution for me so far since I cannot downgrade the mac to Mojave, personal files not belonging to me on it.

Hope to hear from the devs soon about the progress on this.

 

I'm experiencing the same issue and filed a bug case #1192279 with a very simple project that reproduces the issue.

Recreating the same project in 2018.4 LTS and everything works as expected.

 

I change UnityShaderCompiler and build success but run game on Iphone game show a black screen only.
I can still click the button and still sound

 

I'm using 2019.2.9f version in macOS Catalina. I experienced same issue

(Modified) It was just shader issue. mobile shaders are malfuncioning

 

I'm experiencing this on 2019.2.9f1 building for WebGL. The build "succeeds" with a ton of similar shader compiler errors, and when opening the build the only thing that appears is the background. I was experiencing extremely poor quality builds with this, but now nothing appears at all (other than the background of the game).

 

Disabling Auto Graphics API and forcing it to use OpenGLES3 did not work. Same error.

Any other work arounds? This problem has been there for some time now.

 

Just here to report the same issue on 2019.2.10f1 on Catalina

 

I have the same issue on 2019.2.10f1 on Catalina!

 

[QUOTE = "konsordo, 게시물 : 5113274, 회원 : 322793"] Catalina에서 2019.2.10f1에 대해 같은 문제가 있습니다! [/ QUOTE]

Me, too.T.T

 

I can't find this path directory on mac os Catalina. Can you help me?

 

Ok, I found the required folder. You just need to right-click on Unity icon and select second point ~show package content and then go to Contents/Tools/UnityShaderCompiler.exec

 

2019.2.11f1 did not resolve this issue...

My first build after deleting my library folder gave the same errors. I thought it might be working after the errors went away on the next build, but I get a black screen when I deploy to a device, and an assortment of shader errors in the Xcode output window.

I tried using the 19.3.0b8 UnityShaderCompiler, but that didn't solve the issue.

 

This DOES work on 2019.2.11f1! I am running on an iPhone as we speak. Thanks @Domas_L!

 

This does not work on 2019.2.11f1, i can't build it for android. What did you specifically do? I tried to replace the unityshadercomplier but that just crashed my unity and i have to reinstall. Just untick auto graphics api and only have OpenGLES3 in the list right? Doesn't work for me, it still have shader build error.

I tried to build and run again, it successfully manage to build to the android device, but after i open the app, it only shows black screen with weird red rectangle for an intro video scene that i put before the scene with vuforia AR, no sound nothing, then the red rectangle goes away(i assume it went to the next scene) and the whole screen just turn black and nothing

 

Just upgraded our project to Unity 2019.2.11f1 and started experiencing this same issue, none of the shaders work on my iPhone 11 Pro. Halp!

 

Using OpenGLES3 as a workaround does work as intended, but the game's FPS is around 10-15 on my iPhone 11 Pro, where as previously with Metal it was a solid 60.

 

Don't replace the UnityShaderCompiler, use the one that ships with 2019.2.11f1. Delete the Library folder and then open the project allowing everything to re-import. Try building (not build and run) a few times. I got errors at first, then they went away on later attempts to build. Then I unchecked Auto Graphics API in build settings, and I removed Metal (this is iOS only), so OpenGLES3 is at the top of the list, and OpenGLES2 is the only other option below it.

Build and run, and it works. That's exactly what I did for iOS, much of which may not be necessary, but you asked for it.

EDIT: Wanted to try an android build for you, but I am getting unrelated errors that I don't have time to address at the moment. Sorry.

 

@gtzpower didn't you notice any drop in performance? My game is 60fps on Metal, but about 15fps on OpenGLES3. :/

 

One question... WTF???
I updated the Mac a week ago and am now trapped because the workaround is degrading performance, upgrading to 2019.3.0b9 does not help, as there are even more undefined errors, and any version 2019.2x on Catalina leads to shader errors. Replacing UnityShaderCompiler does not completely fix the problem, the project is building, but crashes in purple colors ...

 

And choosing only OpenGLES3 doesn't work for me. Because I developing an AR game with AR KIt package witch support only Metal.

 

I had too many issues with Catalina, Unity shader complier, NDK permission issues, visual studio hang-ups, ui corruptions, also issues with mail & photos apps, etc. So, I give up and as of yesterday I've reverted back to Mojave...

 

THE SAME ISSUE HERE ON unity 2019.2.11f1 !!!!! WTFFF??
I need to release my game already, all the promo dates are set!!!
Unity team, what's wrong with your curly hands??
Also I can't revert the version of unity to 2019.2.9f1 where was no issue with it! i've downloaded the version installer from unity archive, but it don't want to install on Catalina drive (a yellow warning triangle on it)...
damn!

 

Also facing the same issues on 2019.2.11 and Catalina. Switching to a linear Color Space allows me to build for IOS but then I face issues with itunesConnect complaining about giving up support for some older devices.

Using UnityHub to switch revert to 2019.2.9 doesn't resolve the issue either.

 

when I trying to switch to linear colorspace the unity just freezing

 

I just lost a couple days of work ... trying to figure out why my application doesn't work on iOS...
UNITY - WTF?!!?!? Now rollback to 2018 ... It is a very costly "feature"! Is there only one way to get UNITY attention >>
Stop paying and move to another platform?

 

I am thinking about it too

 

I got the issue with 2019.2.22f1. I am using Catalina MacOS. My scenes become GREY after switching platform to iOS. Not only getting grey in my compiled iOS app, my Unity scenes shows image/video/.. as PINK. Finally, I could temporary fix by below steps
1. Build Settings
2. Player Settings
3. Player tab / Other Settings
4. Change "Color Space" from "Gamma" to "Linear"
5. Uncheck "Auto Graphics API", and use "Metal" under "Graphics APIs"
Hope this help !

 

Tried this. While it doesn't give any error logs, and can be deployed to a test device, all textures come out as blank panels only and the app quickly crashes within a few seconds.

Only switching to Linear workflow seems to produce a workable build.

 

@stansison correct, Linear color space doesn't fuk up the shaders and still have a high FPS, but produces a completely different look at least in our game (all colors went very pastel/bland).

 

Same issue here on MacOS Catalina and latest Unity 2019.2.12f1, lot's of shader compile errors on Android build after update project, on 2019.1.10f1 it works.

 

Same as 2019.2.12f1, I have to build my iOS version in windows, use Mac to compile. Waste my time.

 

I was running 2019.2.10f1 and had the same error when building on macOS Catalina Ver 10.15.1
I downloaded the new beta 2019.3.0b10 and it resolved the shaders problem. I tried to build it for ios and tested on my phone, it worked fine. thank god.