Hangs while trying to Build & Run for Android

[JoeStrout]

I’ve just joined a large project, and now I’m trying to compile for Android (Oculus Go). For starters, I have a made a minimal scene consisting of a plane, a handful of cubes, and the default camera and directional light. That’s it.

I set the build target to Android, added my scene, and unchecked the others (so my minimal scene is the only one in the build). I have my device plugged in. But when I try to Build & Run, the progress bar gets to about 20% and then goes no further. Unity is not completely locked up at this point; I can still drag the “Building Player” floating window around. But when Unity is frontmost, I get the rainbow spinning cursor, and I’m not able to cancel the build.

The editor log shows nothing much, though there are lots of errors on shaders I’m not using. The tail end of the log is:

Launching external process: /Applications/Unity 2017.3/Unity.app/Contents/Tools/UnityShaderCompiler
Launched and connected shader compiler UnityShaderCompiler after 0.03 seconds
WARNING: Shader Unsupported: ‘VRTK/AdaptiveQualityDebugVisualization’ - Pass ‘’ has no vertex shader
WARNING: Shader Unsupported: ‘VRTK/AdaptiveQualityDebugVisualization’ - Setting to default shader.
WARNING: Shader Unsupported: ‘VRTK/OutlineBasic’ - Pass ‘’ has no vertex shader
Shader ‘Oculus/OVRMRCameraFrameLit’: fallback shader ‘Alpha-Diffuse’ not found
WARNING: Shader Unsupported: ‘Hidden/Post FX/Depth Of Field’ - Pass ‘COC TEMPORAL FILTER’ has no vertex shader
WARNING: Shader Unsupported: ‘Hidden/Post FX/Eye Adaptation’ - Pass ‘’ has no vertex shader
WARNING: Shader Unsupported: ‘Hidden/Post FX/Eye Adaptation’ - Setting to default shader.
WARNING: Shader Unsupported: ‘Hidden/Post FX/Temporal Anti-aliasing’ - Pass ‘’ has no vertex shader

And it gets no further, no matter how long I’ve let it sit. I let it go for about 40 minutes the first time. I’ve since force-quit and retried twice, and it appears to hang at this same point each time.

I’m running Unity 2017.3 on macOS 10.13. Any idea what might be wrong here, and what I could try to fix it?

[JoeStrout]

Hmm, I thought those shader errors were spurious, but maybe not; Activity Monitor shows a bunch of UnityShaderCompiler processes which are consuming large amounts of CPU:

And if I force-quit one of those shader compiler processes, Unity just relaunches it.

So, shoot. How do I tell Unity “ignore these shaders that I’m not using, and just build the friggin’ game”?