2. Package and prepare a Fission iOS app for TestFlight
Set a stable bundle ID and an explicit marketing version and build number.
The bundle ID must match the registered application, and each uploaded build
needs a new build number. Keep the signing certificate in Keychain and the
provisioning profile outside the repository. App Store Connect API credentials
are separate from application signing credentials.
[package.ios]
bundle_id = "com.example.northstar-journal"
marketing_version = "1.4.0"
build_number = "42"
team_id = "YOUR_TEAM_ID"
provisioning_profile = "/private/signing/Journal.mobileprovision"
Use the selected distribution profile and identity, not placeholder credentials:
fission readiness package --target ios --format ipa --release --project-dir .
fission signing status --target ios --project-dir .
fission package --target ios --format ipa --release --project-dir . --json
Read the emitted artifact manifest and inspect its IPA, source revision and
signing inputs. Do not substitute a Simulator package or an older file with the
same name. The iOS packaging guide
explains the supported signing setup.
An App Store Connect distribution build is uploaded for TestFlight or App Store
distribution. Direct installation on registered devices uses a development or
Ad Hoc build instead; these are different signing paths. See
Apple's distribution methods.
The compiled preview changes browser-local state only; it does not perform this task on the iOS Simulator or an iPhone, inspect your toolchain or access native hardware. Use the commands below to verify the generated project on the target.
Show the app previewHide the app preview
Show the app preview
Hide the app preview