Search Unity

  1. Unity 2018.3 is now released.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. We've updated our Terms of Service. Please read our blog post from Unity CTO and Co-Founder Joachim Ante here
    Dismiss Notice
  4. Want to provide direct feedback to the Unity team? Join the Unity Advisory Panel.
    Dismiss Notice
  5. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice

Use xcworkspace to build instead of the xcproject

Discussion in 'Unity Cloud Build' started by fox, Nov 15, 2018.

  1. fox

    fox

    Joined:
    Jan 14, 2009
    Posts:
    110
    Hello!
    We are trying to get our UCB working with the branch plugin (https://docs.branch.io/pages/apps/unity/). Our local builds works as expected, but the cloud build throws this error:

    523: ▸ ❌; ld: section __bundle (address=0x0A190000, size=664627644) would make the output executable exceed available address range for architecture armv7
    524: ▸ ❌; clang: error: linker command failed with exit code 1 (use -v to see invocation)

    I´ve been in contact with the developers of the branch plugin, and they asked me to use the xcworkspace to build instead of the xcproject.. But I cant find a way to change this on cloud builds. Is it possible to change that in any way? Would be very glad if someone could point me in the right direction!

    (Using Unity 2018.2.13f1, Xcode 10)
     
  2. ollieblanks

    ollieblanks

    Unity Technologies

    Joined:
    Aug 21, 2017
    Posts:
    120
    I believe Cloud Build should automatically use an xcworkspace file if it is being generated. Can you please confirm that an xcworkspace file is generated in the same output directory as the xcodeproj file when you build your Project locally?
     
  3. AlexNanomonx

    AlexNanomonx

    Joined:
    Jan 4, 2017
    Posts:
    14
    Hi, we just updated to Unity 2018.2.18 from unity 2017.3, and our cloud build is no longer working. We're not using the branch plugin. I did a check and our local build works ok, though it does not generate a xcworkspace file in the same output directory as the xcodeproj file.

    Curiously it posts "publishing finished successfully.", immediately before failing.

    Anyway, any advice to resolve this would be appreciated
     
  4. kosted

    kosted

    Joined:
    Mar 14, 2015
    Posts:
    81
    Hi all, I'm facing the same issue. I don't use the cloud build, but when I build my project for IOS, Unity doesn't generate xcworkspace. How could I do ? Could I build my project with just xcodeproj ?
     
  5. AlexNanomonx

    AlexNanomonx

    Joined:
    Jan 4, 2017
    Posts:
    14
    I don't know if you're still having this problem but, for posterity, the fix was rather simple for us. We updated to 2018.3.0. Hopefully 2018.2.19 or .20 include the same fix.
     
    victorw likes this.
  6. kosted

    kosted

    Joined:
    Mar 14, 2015
    Posts:
    81
    Thanks for your answer. Ok, I will update my unity to Unity 2018.2.19.