Matt Massicotte
xcodebuild's inability to just build against a specific SDK without also knowing which goddamn specific destination to use is such a waste of time I mean just choose one please its been like a decade please why just build it doesn't matter
Apr 4 at 11:35amPhanpy
Show threadRicardo Carvalho4d ago

@mattiem iOS development is frozen on time and everything smell Enterprise Decision.

I am so tired of it. Other languages and tools are much nicer and simple to live with.

Show threadMatt Massicotte4d ago
@rabc don't try to convince me there is good software out there it's impossible
Show threadDmitry Rodionov4d ago
@mattiem my empathy for anyone dealing with Xcode in a CI environment, this uphill battle never ends *hugs*
Show threadSven A. Schmidt4d ago
@mattiem I’m sure you know about the generic destinations you can provide, right? (You can see how we invoke those on @SwiftPackageIndex if you click through to the details of Xcode builds in case you don’t!)
Show threadMatt Massicotte4d ago

@finestructure hmmmm ok so I have tried this years ago, but cannot recall. I just gave it a shot and am encountering this:

"xcodebuild: error: Failed to build workspace XYZ with scheme XYZ.: Cannot test target “XYZTests” on “Any iOS Device”: Tests must be run on a concrete device"

Perhaps this works only for builds but not for running tests?

Show threadSven A. Schmidt4d ago
@mattiem Oh right, that’s got to be it. We only build, we don’t run tests, and it makes sense. Cross-compiling is one thing but when launching, you need a device.
Show threadSam Deane1d ago

@mattiem @finestructure I updated my ActionBuilderPlugin recently to pick a device at CI-runtime, as it was getting on my nerves. Especially annoying when baked into a CI script and then Xcode is updated and the old device no longer exists.

Not sure if I've actually pushed that code into a release yet, but it ends up generating this sort of thing:

https://github.com/elegantchaos/Logger/blob/e0514867a7b2f49f0a0ade1a4a23164b1afa73b8/.github/workflows/tests.yml#L203

Which is ugly, but works. Boiling all that down into something cleaner is on my to do list!

(https://github.com/elegantchaos/ActionBuilderPlugin)

Logger/.github/workflows/tests.yml at e0514867a7b2f49f0a0ade1a4a23164b1afa73b8 · elegantchaos/Logger

Configurable logging for Swift. Contribute to elegantchaos/Logger development by creating an account on GitHub.

GitHub
Show threadMatt Massicotte1d ago

@samdeane @finestructure I have not tried it yet but I *think* that is basically what this is doing internally:

https://github.com/mxcl/xcodebuild

Show threadSam Deane1d ago

@mattiem @finestructure ah, cool!

I’ve been thinking that I should try to turn my plugin into an action as it makes a lot more sense in some ways.

Show threadNathan3d ago

@mattiem i found a fun similar scenario the other day when i launched 26.3 after having moved to 26.4: since i had deleted the highest available iOS SDK for 26.3, thinking that i no longer needed it, i could not build against any SDK, not even lower ones also supported by 26.3 (which was my objective anyway) — i had to download 26.3’s default SDK again before i could choose to build against the lower SDK that i still had.

now it’s just going to take up space on my machine until i’m confident i can delete Xcode 26.3