[Xcode 16.0 Beta] Carthage fails to xcodebuild archive -showBuildSettings, mentions no destinations.
#3375
Comments
|
Note Put up a commit. Commit description details more. Try it out (at one’s own discretion) with How we researched this (historical info from mid-2024.)Going to look into this¹, drawing context (first off) from:
⑴ Probably involves me filing in Feedback Assistant. But if I find success with 'modify the carthage code'-based options, I may post a prototype carthage homebrew formula. |
|
@henrik-dmg just to be thorough in asking questions — any chance the iOS platform had not yet been installed when this run happened? Sometimes there's a window like: Note Help us grab debugging info: as soon as you first see the above issue, if you were already planning to download the iOS platform (sometime colloquially called iOS SDK), then run and grab the following: |
xcodebuild archive -showBuildSettings CocoaLumberjack, mentions no destinations.
|
Thanks for your quick reply. No, the iOS SDK was definitely installed the Xcode 16 Command line Tools were selected |
This comment was marked as resolved.
This comment was marked as resolved.
|
We have a similar issue in our project as well.
We run |
…ix `-showBuildSettings` with solely the `archive` action. No longer (under Xcode 16 and above) leave `OBJROOT` as stands. Deal with error ‘Found no destinations for the scheme [^\n]+ and action[…]’. No longer (under Xcode 16 and above) prefix `-showBuildSettings` with solely the `archive` action. Carthage has long-standingly built `simulator` code under the `build` action, but (due to certain now-believed-to-be-fixed bugs, had historically passed the `archive` action when querying under simulator destinations for Xcode Build Settings.) Such a ‘discrepancy which Carthage relies upon improper values out of alignment with Xcode action verb,’ we now believe no longer works around any bugs and Xcode 16 (beta 1 (16A5171c) at the very least) now returns ‘proper’ Build Settings for simulator destinations and the `archive` action. Xcode Build Setting `OBJROOT` now appears to have more path components. We lop some off (only under Xcode 16 and above.) Out of the three here, Carthage authors are most unsure about leaving this code change ‘as it stands.’ Especially under the purview of Carthage setting `--derived-data`. I’ll comment in the below link as actually running Carthages tests (unit and integration) should ‘prove out’ its sufficiency or deficit. PRs welcome. Under all Xcode versions, all xcodebuild invocations of `-showBuildSettings` that return non-0 exit code and standardError matching `error[:] Found no destinations for the scheme [^\n]+ and action [^\n]+[.]\n` will see non-surfacing of those errors. Carthage proceeds as if that xcodebuild invocation never happened (which is essentially how Carthage behaved before it had one more non-0 exit code return to deal with.) `brew install carthage --head` is a pathway that exists (attempt at one’s own discretion, and use the internet for associated prerun commands such as `brew uninstall` and others.) 〜 As several CI providers no longer provide both ‘VNC access’ and Intel Mac builders, Carthage currently has no CI. Carthage maintainers shall be fixing this and commenting in the below link (and elsewhere.) Potentially fïxes Carthage#3375. Potentially fïxes Carthage#3374. See Carthage#3374 for future updates on sufficiency of this commit, and whether lack of ‘may be reverted’ stands.
|
Put up a commit. Commit description details more. Try it out (at one’s own discretion) with 〜 Carthage maintainers will have to restore CI (to test, unit and integration style) before we ship it. Details in the commit description. We have a plan in mind. |
xcodebuild archive -showBuildSettings CocoaLumberjack, mentions no destinations.xcodebuild archive -showBuildSettings, mentions no destinations.
This comment was marked as resolved.
This comment was marked as resolved.
|
@jdhealy following your steps I was able to build |
|
Seems to fail when specifying Something wrong with the platform scheme lookup or something? |
|
@wrutkowski-tyro yes, great to have you post that feedback (on has no shared framework schemes for any of the platforms: iOS). Thank you! Helped us find an additional bug 🎉 , which — it being a separate issue — gonna link there and hide the comment to allow folks consuming all |
|
@einar-notland, we put up another commit. Good chance we fixed what you’re hitting. Try using the below: Note Put up a second commit for June. Commit description details more. Try it out (at one’s own discretion) with |
|
@jdhealy Thank you so much. The latest commit seems to fix the problems we have seen related to using |
|
I believe this is broken again in Xcode 16 beta 6 ( |
|
@dustinburke-gh Yes, same issue here, head version does not help |
|
The output message from xcodebuild has changed, so the pattern introduced in the previous fix no longer matches. Before it was e.g.
Changing it to skip the new string makes it work again with Xcode 16 beta 6 (or the new string can be added to the pattern). -let pattern = "error[:] Found no destinations for the scheme [^\n]+ and action [^\n]+[.]\n"
+let pattern = "error[:] [^\n]+Found no destinations for the scheme [^\n]+ and action [^\n]+[.]\n" |
|
@jdhealy are there any estimates when a new release will be created? |
|
Tested @apoltix's changes. It works locally. Raised a PR with his suggestion. |
which carthage:/opt/homebrew/bin/carthagecarthage version: 0.39.1xcodebuild -version:Xcode 16.0 Build version 16A5171c--no-build? No--no-use-binaries? No--use-submodules? No--cache-builds? No--new-resolver? No--use-xcframeworks? YesCartfile
Carthage Output
Actual outcome
Carthage fails to build CocoaLumberjack because it seemingly tries to build an iOS unit test scheme that has no run destinations (project
Tests/Tests.xcodeprojin CocoaLumberjack repo)Expected outcome
Carthage should build CocoaLumberjack correctly
The text was updated successfully, but these errors were encountered: