XCode 12.5 in UCB?

This is how useful Unity Cloud Build is for us at the moment

 

Can we get an update on the estimated date that this will be available, from someone at Unity?

Also, will xCode 13 be available in Unity Cloud Build as well?

 

To add context to the importance and urgency of this, major third party components are dropping support for Xcode 12.4, such as Google's Ad SDK for Unity. It is currently impossible to build an iOS app which uses this extremely popular library. It fails due to bitcode mismatch, and the only solution is to upgrade to Big Sur.

https://github.com/googleads/googleads-mobile-unity/issues/1677#issuecomment-875525106

 

Hey, you said September. It is September ...

@smithmj5 For xcode 13 I created this other thread https://forum.unity.com/threads/xcode-13-eta.1130497/ I you want to get no information as usual you can follow ...

 

Oh noo I just saw this thread : https://forum.unity.com/threads/update-on-xcode-12-5-and-13-0-timing.1165295/
(Why don't you guys don't answer in the existing forum thread that we are following ?? )

For everyone here, the short answer is

12.5 supported by the end of September 2021 and 13.0 shortly after its official release by Apple
​

For unity team , i mean ... do you guys really understand the urgency ? Your tool is just broken for quite a big party of your users , but take your time...

​

 

Apple will be happy. After reading that, I just ordered a Mac Mini M1 ..

 

...thus endless loop continues. Frankly, whole their ecosystem is complete steaming pile of ...


Anyway. By the time v12.5 comes online with UCB we'd need v13.
UCB should provide XCode beta versions as well. Otherwise we'd get stuck with the same problem and v14.

 

BUMP

As always I see the Unity from their "best" side...
Now imagine: You should go to your employer and explain to him that this is not your fault and get reaction like: "How others making their builds for iOS with Unity?", while UCB was the only option to make iOS builds for a lot of developers.

Such services and engines had better never exist. But now we are in a situation where we are very dependent on them. Draw conclusions.
*Must die*

 

They said "by the end of September" - however the lack of keeping us (the customers) up2date is just ridiculous.

I never experienced something more unprofessional than this. Unfortunately we're kind of bound to UCB as we're a small team and can't afford other CD solutions (yet).

Well, let's see what happens in three days....

 

Well, if Apple changes their licenses and you need to upgrade your whole infrastructure to support the new operating system and make sure, that thousands of existing projects do not break, have downwards compatibility, etc.
I sure would make sure, that everything runs as smooth as possible and this takes time.

You call it unprofessional, but you're not even able to switch to another CD yet. GitHub Actions are free (at least for public repos), you can easily use them instead of UCB. For private repos you get 2000 action minutes for free, thats 33 build hours per month. Not that much, but it's something to start and you can add credits later. Since you are so much more professional, it should be easy for you to setup it up, because it's only for your projects and not thousands of them...

I'm also waiting on UCB to have 12.5 and 13 ready, but I totally understand, that this is a big task. So, I do not blame Unity, but give them the time they need to upgrade their whole MacOS-based infrastructure.

Gosh, just give them time to do it right instead of blaming them the whole time.

Edit: The only thing I agree is the lack of communication. I do not care, if it takes longer than expected, etc. as long as someone communicates. Current progress, current struggles, etc. One information every two weeks, that would help.

 

Listen: this is not an our idea to play in the "business" - thats the choice of Apple(with all of their licenses and encrypted software) and Unity too, as Unity-tech keeping their technology closed and even has paid services. If so then be prepared to get such reactions. Why we should to go in "understandings" when Unity-tech never care about our? They gives us the full right to push them on their head, this is not an our mistake.

I want stop to talk for others, but in the end will say for me personally: I will never tolerate such companies, they does not deserve my patience, its already tooks too much of it.

 

Well, quite easy then: Don't use Unity and use another engine, if you are not happy with it.
Other services will also have some interruptions, that's something you have to expect.

 

Like some others, I started using Unity3d before I had that understanding. Now it's not that easy to just leave an engine that you have a lot of experience with.

 

As you are an professional, you can learn other engines. Most of the basic concepts are the same.

 

Thanks @Grazer2 I can confirm that:
AdHoc and Enterprise wont install with XCode 12.4 on iOS 15. This gives the error that the app needs to be upgraded.
Testflight does install with XCode 12.4 on iOS 15. It can be safely assumed that Appstore should be good.

The issue is that for most developer code-build-test-debug cycles on an iOS device AdHoc is the preferred route, with some teams using Enterprise. It is far easier to deploy to the test device using AdHoc or Enterprise from the Unity Cloud Build share link than to have to deploy to Testflight to perform each iterative test. Also we have AdHoc / Enterprise builds communicating to QA rest services while Testflight and Appstore communicate with PROD rest services. Our dev and test pipeline is in disarray now.

https://unity-technologies.github.io/cloud-build-docs-public/xcode-unity-versions-compatibility gives the indicated date as end of today for XCode 12.5 (which will resolve, along with 13.0). Has anyone seen 12.5 on the Unity Cloud Build, or seen hints of the end of September 2021 ETA not being met, so that we can plan accordingly? @Danny327

 

Hey guys, I opened a new thread asking about any time estimations update since September is already over.
https://forum.unity.com/threads/xcode-12-5-in-ucb-time-estimations.1176509/

 

Moving platforms from Unity to another engine is a massive undertaking for a shipping game. You can't do it overnight.

Besides, this is not "some interruption". This is an important continuity of service feature that Unity has been dragging their feet on implementing for over a year. It isn't an unforeseeable outage. We pay Unity a monthly fee for this service, and it's stopped meeting our needs because they haven't kept it up-to-date. Even if there are alternatives, it's completely reasonable for us as paying customers to point this out and express our frustration. What's more, Unity explicitly committed in writing to a timeline for supporting this feature, and they've yet to deliver. (EDIT: now they've pushed back to end of October, but that we shouldn't count on that date, either)

I agree the person you were responding to was being overly dramatic, but not let's blame ourselves for expecting reasonable things from a paid service provider.

 

Where did you hear end of October? I can't find the announcement.

 

From here: https://forum.unity.com/threads/xcode-12-5-in-ucb-time-estimations.1176509/#post-7538552
Another forum user submitted a support ticket and was told "we aim to have 12.5 released in the mid to the end of October. Please note that this is not an official release date and could change."

 

Thank you @rajivrao!

 

I tried to switch to 12.5.1 using an existing config but the version does not show up as you can see below. It does appear if I create a new config. Is this intended?

Thanks