Any ETA for Xcode 13.3.1 support?

Unity Services
,
1

Cannot update to the new Firebase version because the iOS builds fail.

8151743--1058975--upload_2022-5-24_9-47-7.png
8151743--1058975--upload_2022-5-24_9-47-7.png920×391 38.8 KB

2

Would love to know that also, maybe Unity Cloud team could think of page for upcoming sdk updates.

3

I came here also looking for that.

We mistakenly updated our Firebase to v9.0.0 and got this error on UCB:
504: ▸ :x:; ld: could not reparse object file in bitcode bundle: ‘Invalid bitcode version (Producer: ‘1316.0.21.2.3_0’ Reader: ‘1300.0.29.30_0’)’, using libLTO version ‘LLVM version 13.0.0, (clang-1300.0.29.30)’ for architecture arm64
505: ▸ :x:; clang: error: linker command failed with exit code 1 (use -v to see invocation)
506: ▸ Copying FBLPromiseError.h
507: ▸ Compiling FBLPromiseError.m
508: ▸ Compiling FIRInstallationsHTTPError.m
509: ▸ Compiling FIRInstallationsErrorUtil.m

I believe this was caused by the same issue, is that right?

4

@ollieblanks Could you direct us to the page where the roadmap can be found for updates to build tools and Unity versions? We are evaluating Cloud builds and must of course make sure that the latest version is always available. I am sure this was an isolated incident that is corrected with the utmost urgency, right? As I said I am just making sure that we will always be able to build if we were to commit to this, as build servers are critical company infrastructure.

Thank you.

5

8164445--1062068--upload_2022-5-28_23-0-3.png

6

@MikeSaverUnity could we get Unity update on this issue?

7

Any update here?

8

We are also having this problem :frowning:
Bump!

9

Still no updates?

10

The lack of support on this initiative made us decide to not use this service, but thank you anyway. We can not commit to a build system where we don’t have control over the Unity and Xcode versions and where they are not instantly installed as they become available, nor is it clearly communicated when it will happen. Things seem too random and it appears as the Cloud Build is only aimed at hobbyists at this stage, which of course makes it impossible to commit to right now.

11

@scotth-unity @MikeSaverUnity @wrossmck-unity
Can one of you please comment on this? We don’t need you to update xcode right away, we already know it’s an issue based on the last 2-3 years of dramas. What’s really making it look bad is the lack of communication.
Give us an ETA so that we could know if it’s worth waiting for us or should we consider downgrading Firebase. Just a rough plan would be fine.

12

Hi folks, we are working on landing in 13.3.1 and 13.4.0 which are both currently going through our automated validation tests. We are also working on some tech and process to roll out new Xcode and OS versions faster.

We’re hoping to land this in the coming weeks, but I’m hesitant to make a timeline commitment

13

Thank you for the communication, it is appreciated. Now that it’s been 3 weeks since your last post, can you provide another update on ETA? Understood if you’ll need more time, but this is important for many of us for planning purposes, particularly as Firebase dropped support for Xcode < 13, meaning that any project using the latest stable version of Firebase will fail to build under Unity Cloud Build today.

14

I am also getting this exact error when building with cloud build with the new version of Firebase. Local build works fine. Please remedy!

15

Just checked in with the team and we have this live in our staging environment. It’s looking like it won’t land for at least 2 more weeks, but getting very close now. This has been delayed due to some complications in how we are rolling out Monterey images.

totally acknowledge we are waaaay behind schedule here. We’re working to streamline this for the next OS and Xcode (and android sdk) releases.

16

Thanks very much for the communication and transparency! I wish you and the team best of luck in the final productionization push.

Btw, might be worth considering whether there would be value in (eventually) opening up a pre-production environment to the public. I think I probably speak for many folks here when I say we’d be happy to try running our builds against a newer, unstable environment. It would give us an early preview of possible incompatibilities, and probably help us help you move more quickly and with greater confidence, catch bugs earlier, etc. Obviously I realize setting up a public test environment would be relatively big lift and so it wouldn’t help with the rollout at hand, but might be something worth evaluating for future releases!

17

this is a great idea which I support.

Right now we have some complications in how we’re handling the cloud build configs that make this more challenging to roll out. We currently make some decisions on the users behalf (sometimes at runtime) which makes it more challenging/risky to introduce new “experimental” versions of things like android sdk, new operating systems, Xcode versions, etc.

The plan is to codify that in the configs so that users are fully in control of what execution environment a build runs in. that is other work that has started but it isn’t where it needs to be to have a smooth rollout of new versions. We have started to lay the foundations of this “immutable configs” idea though, so you can expect more changes in this area over the coming months.

It’s a trade-off between simplicity and exposing the complexity. in the past we were very careful not to expose so much complexity but that just meant there was lots of hidden complexity which didn’t really help folks either.

18

Any update here?

19

+1 Any update on that version? i’m needing to upgrade admob and firebase and i’m unable to do that because this.

20

Good day! Can you please let us know when x code 13.3.1 will be updated? We are not able several SDK (firebase, iron source, etc).

Honestly speaking, it is not the first time when UCB blocks us for more than a month. It’s pretty frustrating…:frowning: Hope you will find a way to deliver x code update faster.