Search Unity

Unity 2018.3 IOS Build Fail

Discussion in 'Unity Build Automation' started by travispettry, Mar 20, 2019.

  1. travispettry

    travispettry

    Joined:
    Jul 21, 2017
    Posts:
    25
    Hi All,

    I just upgraded my Unity project to 2018.3.9. Even since I have done the upgrade the Cloud build has been failing. I am getting the following errors:

    Compact Log:
    2: ! platform service error: read timeout reached
    342: [0320/134709:ERROR:mach_broker_mac.mm(268)] Unknown process 7346 is sending Mach IPC messages!

    Full Log Differences:
    12066: (1 failure)
    12067: Exit status: 65
    12068: Maybe the error shown is caused by using the wrong version of Xcode
    12069: Found multiple versions of Xcode in '/APPLICATION_PATH/'
    12070: Make sure you selected the right version for your project
    12071: This build process was executed using '/APPLICATION_PATH/Xcode10_1_0.app'
    12072: If you want to update your Xcode path, either
    12073: - Specify the Xcode version in your Fastfile
    12074: ▸ xcversion(version: "8.1") # Selects Xcode 8.1.0
    12075: - Specify an absolute path to your Xcode installation in your Fastfile
    12076: ▸ xcode_select "/APPLICATION_PATH/Xcode8.app"


    Does anyone know what these errors are?

    Thank you,
    Travis Pettry
     
  2. oskar-szulc

    oskar-szulc

    Joined:
    Feb 22, 2013
    Posts:
    6
    Same here, 2018.2 works fine, also building locally works ok with 2018.3. Wasn't able to get any help so far.
     
  3. szatletsdigital

    szatletsdigital

    Joined:
    Oct 28, 2018
    Posts:
    1
    I have the same problem. I contacted Support concerning this issue. I hope they'll be able to help.
     
  4. andersemil

    andersemil

    Joined:
    Feb 2, 2015
    Posts:
    112
    I'm guessing that your target is configured to use a very old Xcode version (8.1.0). Upgrade it to latest Xcode version. (Unity 2018.3 outputs for Xcode 10)
     
  5. oskar-szulc

    oskar-szulc

    Joined:
    Feb 22, 2013
    Posts:
    6
    It's not the case for us, we've been running on Xcode 10.1 while building with 2018.2, and it started failing after switching to 2018.3. Btw, it fixed itself today for one build (just after updating Firebase to 5.6.0), but then broke again.
     
    andersemil likes this.