Search Unity

  1. Get all the Unite Berlin 2018 news on the blog.
    Dismiss Notice
  2. Unity 2018.2 has arrived! Read about it here.
    Dismiss Notice
  3. Improve your Unity skills with a certified instructor in a private, interactive classroom. Learn more.
    Dismiss Notice
  4. ARCore is out of developer preview! Read about it here.
    Dismiss Notice
  5. Magic Leap’s Lumin SDK Technical Preview for Unity lets you get started creating content for Magic Leap One™. Find more information on our blog!
    Dismiss Notice
  6. Want to see the most recent patch releases? Take a peek at the patch release page.
    Dismiss Notice

Hangs while trying to Build & Run for Android

Discussion in 'Editor & General Support' started by JoeStrout, Jul 11, 2018 at 10:35 PM.

  1. JoeStrout

    JoeStrout

    Joined:
    Jan 14, 2011
    Posts:
    6,872
    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:

    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?
     
  2. JoeStrout

    JoeStrout

    Joined:
    Jan 14, 2011
    Posts:
    6,872
    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:

    upload_2018-7-11_14-39-59.png

    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"?