chore: automate personal iPhone previews - #6
Draft
musepy wants to merge 1 commit into
Draft
Conversation
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
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.
Summary
Why
The previous device-preview attempts mixed up the certificate label suffix and Xcode development team, tried to launch a standalone Flutter Debug build, reused path-bound CocoaPods output, and initially missed an unsigned nested framework. This made a visual review unnecessarily slow and easy to repeat incorrectly.
The new workflow derives the team from the selected certificate, rejects the project-owner team and canonical bundle ID, regenerates Flutter/CocoaPods files inside an ignored isolated workspace, verifies the final signature and embedded provisioning profile, then installs and launches the Profile/AOT app by exact bundle and process path.
Safety and impact
Verification
flutter pub get --enforce-lockfileflutter analyze --no-fatal-infos— passed with 13 existing info diagnosticsflutter test— all 20 tests passedNote
The locally verified personal provisioning profile expires on 2026-08-05; the script rejects expired profiles and warns when fewer than seven days remain.