Compose MP seems to not have the x86_64 target, an...

# compose

[Stylianos Gakis]

Compose MP seems to not have the x86_64 target, and hasn't had it for quite a long time now actually.
And coincidentally, tests run on the iOS side using Xcode cloud seem to only run on a simluator configured like this Xcode Cloud runner host arch: x86_64 with no option to swap to an arm alternative instead.
Does this mean basically we are out of luck regarding continuing to use Xcode cloud to run our iOS tests if we want to start sharing compose code in our shared library?

Has someone else encountered this before, did you just have to drop either sharing Compose code or running the tests on Xcode cloud as I assume?

[jw]

Google was a bit too eager to remove it from their published artifacts which sucked.

[jw]

Once they removed it, all downstream projects had to follow suit.

[Stylianos Gakis]

Well that means I need to now either convince my iOS devs to swap off of Xcode cloud
Or to just stop the project of trying to share CMP code with them 🫪

[Stylianos Gakis]

Excellent gambit laugh cry face palm

[Stylianos Gakis]

Or to wait for apple to swap the old simulators for arm simulator instead when running tests there. Or at least make that configurable I guess

[hfhbd]

Google should bring back iOS x86_64 which isn’t deprecated anymore.

[Stylianos Gakis]

I've filed two issues for this:
JetBrains: https://youtrack.jetbrains.com/projects/CMP/issues/CMP-10263/Bring-back-x8664-target-for-Jetpack-Compose
Google: https://issuetracker.google.com/issues/518435522

I am afraid that's all I can do. If you have any input on either of those please do add it, I am sure it will help

[Stylianos Gakis]

Maybe Xcode is also going to ditch the intel targets after all. If I understand correctly this would solve my problem here, if Xcode Cloud is then also forced to ditch the intel target
developer.apple.com/documentation/xcode-release-notes/xcode-27-release-notes#…