Use xbuild and official CPython support packages for iOS. - #3071
Merged
Merged
Conversation
This was referenced Sep 22, 2026
mhsmith
approved these changes
Sep 23, 2026
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Modify the support package specification to use the official CPython iOS support packages for 3.15+
As part of this change, adopts the use of xbuild for creating the cross-platform virtual environment for iOS projects.
Fixes #3070.
Pairs with the template update beeware/briefcase-iOS-Xcode-template#88, but Briefcase CI runs app tests using Python 3.12, so it doesn't require the changes in the template to pass.
Also includes a small addition to the bootstrap apps. In the process of running this in CI, I initially got some weird results which suggested the app wasn't starting, so I added some debug at the start of the automation app so that we get a signal as soon as practical that the app is going to start. This would have been useful for the Windows stability testing as well, so I've included it as a general improvement.
PR Checklist: