XCode 12.5 in UCB?

[paradizIsCool]

Is there an eta to support XCode 12.5 in UCB?
Our ad sdks just raised the minimum version to 12.5

[Kujo87]

same issue here - using Fyber and requires 12.5 as minimum now for some iOS 14.5 stuff

[Danny327]

Thank you for reaching out in Unity Forum.
Unfortunately, due to Apple’s new policy, it requires us to upgrade to our build OS to Big Sur and we are actually in the process of doing this but it’s still a little while away. So, no ETA at the moment.

[paradizIsCool]

Just thinking about that message right now

@bradunity

Hello all!

After attempting many different approaches at supporting newer versions of Xcode that require macOS Catalina (v10.15) within Cloud Build’s infrastructure, we have landed on a solution. We are actively engaged in the final validation and all signs indicate that it will be made available for everyone in mid December, supporting the following versions of Unity:

• 2017.4.33f1 and later
• 2018.4.10f1 and later
• 2019.3.0f1 and later
• 2020 and later
• 2021 and later

We are sincerely sorry for how much longer this effort has taken than previous years. Anticipating the need for macOS Big Sur (v11), we have already scheduled evaluation and testing in the first quarter of next year to avoid this type of problem.

from https://discussions.unity.com/t/805477

[StormChaserDev]

This is very unfortunate! We just started using UCB and this breaks our current iOS build. We had to update one of our 3th party tools which uses Xcode 12.5 because of the iOS 14.5 update.

Really need this support asap.

(edit): There’s not even support for Xcode 12.4 in UCB?

[Danny327]

Thanks for sharing. Please stay tuned for our upcoming updates for Xcode 12.5 support!
As for Xcode 12.4, it has been in the list of supported versions for quite some time now. (see screenshot)

When was your screenshot taken?

[Medhaedu]

Any ETA On 12.5 . As it hampers our Qa testing and releases.

[StormChaserDev]

@Danny327

Thanks for sharing. Please stay tuned for our upcoming updates for Xcode 12.5 support!
As for Xcode 12.4, it has been in the list of supported versions for quite some time now. (see screenshot)

When was your screenshot taken?

Thanks for the reply. My screenshot is just a couple of days old. I also attached one from just now. As you can see we don’t see Xcode 12.4 in the list.

(edit): I think I found a bug → My target configs are copied. When I create a new target for iOS I can see Xcode 12.4 in the list

however, our build still fails because of a 3th party plugin was build using Xcode 12.5 so we really need this asap

[fiveampsoftware]

Our latest build was just rejected by Apple due to being built with 12.4. Their info:
ITMS-90424: Invalid Swift Support - The SwiftSupport folder is empty. Rebuild your app using the current public (GM) version of Xcode and resubmit it.

[Danny327]

@StormChaserDev

Thanks for the reply. My screenshot is just a couple of days old. I also attached one from just now. As you can see we don’t see Xcode 12.4 in the list.

(edit): I think I found a bug → My target configs are copied. When I create a new target for iOS I can see Xcode 12.4 in the list

however, our build still fails because of a 3th party plugin was build using Xcode 12.5 so we really need this asap

Thank you so much for sharing the bugs. Let me go ahead and relay this to the relevant communication channel internally.

As far as the availability of Xcode 12.5, all I can say is we are currently working on getting it released. However, since it involves a whole new OS and hardware upgrades, it will be a bit away and we don’t have any specific ETA at the moment.

I hope it helps!

[StormChaserDev]

@Danny327

Thank you so much for sharing the bugs. Let me go ahead and relay this to the relevant communication channel internally.

As far as the availability of Xcode 12.5, all I can say is we are currently working on getting it released. However, since it involves a whole new OS and hardware upgrades, it will be a bit away and we don’t have any specific ETA at the moment.

I hope it helps!

Thanks for the update.

Unfortunately it doesn’t help us because we can’t downgrade the plugin. In this case UCB is not a valid solution for us anymore. It’s really a shame. As a programmer I get how things like these take time. As a paying customer I don’t get how a company can’t focus on their products to keep them up 2 date and don’t even give a rough ETA to their customers.

Like, what does “a bit away” means? 1 month, 6 month, a year?

[rebelincontrol]

Thanks for your response @Danny327 - appreciate the update/work you’re all putting in. I have to agree with @StormChaserDev though. After the 12.3(?) fiasco late last year, I was hoping that there wouldn’t be another delay like it at least for the foreseeable future. As a paid service it needs to be much, much quicker with the rollout. We, along with many other developers no doubt, simply cannot afford to have weeks/months of delays on the latest version of XCode every other time there is a release.

As others have mentioned we don’t have the option of downgrading certain libraries, it’s an absolute requirement that we are up to date. This is something that needs to be dealt with for future releases/upgrades as a matter of urgency if Unity is going to continue selling Cloud Build as a service. It is, unfortunately, currently not fit for purpose.

[Danny327]

@StormChaserDev

Thanks for the reply. My screenshot is just a couple of days old. I also attached one from just now. As you can see we don’t see Xcode 12.4 in the list.

(edit): I think I found a bug → My target configs are copied. When I create a new target for iOS I can see Xcode 12.4 in the list

however, our build still fails because of a 3th party plugin was build using Xcode 12.5 so we really need this asap

I think the issue here is that Unity version bound to the build target does not support xcode 12.4.
You will want to set it to one of the following versions of Unity in order to be able to use xcode 12.4.

* Unity 2017: 2017.4.33f1 and >
* Unity 2018: 2018.4.10f1 and >
* Unity 2019: 2019.3.0f1 and >
* Unity 2020: All versions
* Unity 2021: All versions```

I hope it makes sense.

[StormChaserDev]

@Danny327

I think the issue here is that Unity version bound to the build target does not support xcode 12.4.
You will want to set it to one of the following versions of Unity in order to be able to use xcode 12.4.

* Unity 2017: 2017.4.33f1 and >
* Unity 2018: 2018.4.10f1 and >
* Unity 2019: 2019.3.0f1 and >
* Unity 2020: All versions
* Unity 2021: All versions```

I hope it makes sense.

Thanks for the reply.
We’re using Unity 2020.3.x so this is not the problem. As I said, I was able to select XCode 12.4 once creating a new Build target.

[Agalliaret]

Have same problem.
Our release plans are ruined due to the fact that we cannot build on Xcode version 12.4. Do you have rough plans for adding Xcode version 12.5?

[thibouf]

And here we go again …

ETA for Xcode 11 support?

Hey team! Love Cloud Build. Use it all the time - way better than lugging a million different devices around to make sure my builds are good. My big question is around when support is likely to be added for Xcode 11. For the first time I'm in a situation where I need to develop for the release of ios13 - and honestly I am unsure when y'all typically release support for new versions. My hope is that the Xcode beta would be something we could opt-in to on Cloud Build until the official release…

Xcode 12 eta?

Is there an eta or plan to support Xcode 12 in UCB? I need it to update my games to support the ad identifier changes in iOS 14.

So what about xcode 12.5 ETA ??

[Meatloaf4]

Hey @Danny327 , unfortunately, it looks like quite a few libraries are starting to depend on Xcode 12.5 (for example AdMob 6.0.1) otherwise a bitcode error is thrown and thus cloud build becomes useless.

I definitely understand not being able to give a specific eta but it would be awesome to know a general timeline. Perhaps you can let us know if it’s it will be greater than 3 months to 6 months to get 12.5 implemented?

This would at least give many of us a general idea of what kind of shifts we should be making to our build pipelines in the meantime.

For example, if it’s going to greater than 6 months I would likely figure out an alternate root to get my builds working on UCB Xcode 12.4. Whereas if it’s more in the 3-month range I might just bite the bullet and build locally until 12.5 gets rolled out.

Thanks for keeping us in the loop btw. I really appreciate the time and support.

------ Edit ------

This is a bit unrelated, but the way I got around the lack of Xcode 12.5 for UCB with AdMob package (6.0.1) for Unity is to utilize the release iOS source files in the release .zip instead of the unity-plugin-library.a in the release .unitypackage.

In this case, a picture is worth a thousand words so see the attached images for more info :).

[masterton]

I haven’t tried this… yet… but you can rent a dedicated mac-mini in the cloud - https://www.macstadium.com/ - the cheapest option is $59 and Im sure its slow as molasses but considering I’ve spent 3 days trying to get my ad network sdks to build on UCB I wish I had spent the money.

[unityventures7]

Apparently my problem I posted on other topic is about this as well
Ad networks failing with xcode 12.4 on UCB

[smithmj5]

@unityventures7

Apparently my problem I posted on other topic is about this as well
Ad networks failing with xcode 12.4 on UCB

Same issue here, with ironSource and all mediation adapters. I’ve gotten around it temporarily by manually overriding the iOS version of ironSource and adapters to old versions that didn’t require xcode 12.5, but that’s not a good solution long-term.

@Danny327 Any update on when we might expect to have xcode 12.5 support in Unity Cloud Build?