Search Unity

OSX Cloud Build failure with 2017.3

Discussion in 'Unity Build Automation' started by mgregoirelds, Dec 22, 2017.

  1. mgregoirelds

    mgregoirelds

    Joined:
    Feb 3, 2017
    Posts:
    22
    Hello,

    I recently switcher my OSX Cloud build to Latest 2017.3 as I want my build to match the current version of the editor I am using. For some reasons, I am getting these errors:

    66: [Unity] Build target platform name 'standaloneosxintel64' is not valid. Supported targets: Android, Linux, Linux64, LinuxUniversal, N3DS, OSXUniversal, PS4, PSM, PSP2, Switch, Tizen, Web, WebGL, WebStreamed, WiiU, Win, Win64, WindowsStoreApps, XboxOne, iOS, tvOS
    67: [Unity] Fatal Error! Build target platform name 'standaloneosxintel64' is not valid. Supported targets: Android, Linux, Linux64, LinuxUniversal, N3DS, OSXUniversal, PS4, PSM, PSP2, Switch, Tizen, Web, WebGL, WebStreamed, WiiU, Win, Win64, WindowsStoreApps, XboxOne, iOS, tvOS
    68: [Unity] Aborting batchmode due to failure:
    69: [Unity] Fatal Error! Build target platform name 'standaloneosxintel64' is not valid. Supported targets: Android, Linux, Linux64, LinuxUniversal, N3DS, OSXUniversal, PS4, PSM, PSP2, Switch, Tizen, Web, WebGL, WebStreamed, WiiU, Win, Win64, WindowsStoreApps, XboxOne, iOS, tvOS
    70: + Building Unity player (standaloneosxintel64)
    I've seen that in 2017.3, defines were renamed. Is it possible that Cloud Build is still using the previous 'standaloneosxintel64' define instead of the new one?

    FYI, I created my Cloud Build task for Latest 2017.2 and edited it today to use Latest 2017.3 instead. Previous builds using 2017.2 (before switching) were all fine!
     
    Novack likes this.
  2. dannyd

    dannyd

    Unity Technologies

    Joined:
    Jun 3, 2014
    Posts:
    785
    Actually OSX 32/64 bit platforms are no longer supported in 2017.3 onward. Only OSX Universal. We are working on providing clearer feedback / messaging in Unity Cloud Build specifically, but wont happen until after holidays.
     
    Novack likes this.
  3. Novack

    Novack

    Joined:
    Oct 28, 2009
    Posts:
    844
    Still getting that obscure message, luckily I found this thread. Using Unity 2017.3.0.p3.
     
  4. cdytoby

    cdytoby

    Joined:
    Nov 19, 2014
    Posts:
    181
    It's almost May now, still have this issue. Mayday!
     
  5. iMer

    iMer

    Joined:
    May 21, 2013
    Posts:
    29
    also got caught by this today