-
Notifications
You must be signed in to change notification settings - Fork 134
Add troubleshooting guidance for iOS bundle identifier issue #3320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -323,4 +323,22 @@ If the scheme is correct and shared, add the following command to the Post-clone | |||||
| {{< highlight yaml "style=paraiso-dark">}} | ||||||
| flutter pub get | ||||||
| {{< /highlight >}} | ||||||
| This ensures that all necessary iOS project files are properly generated before dependency installation begins. | ||||||
| This ensures that all necessary iOS project files are properly generated before dependency installation begins. | ||||||
|
|
||||||
|
|
||||||
| ### The bundle identifier cannot be changed from the current value, 'xxx'. | ||||||
|
|
||||||
| ###### Description | ||||||
| When building code signing an ios app, you may encounter the following error in the publishing step: | ||||||
|
|
||||||
| This bundle is invalid. The bundle identifier cannot be changed from the current value, 'xxx'. If you want to change your bundle identifier, you will need to create a new application in App Store Connect | ||||||
|
|
||||||
| ###### Cause | ||||||
| This is an known issue which comes with the recent versions of [altool](https://github.com/fastlane/fastlane/issues/29698#issuecomment-3329783816)(shipped with Xcode 26) which has introduced a bug that can cause binary uploads to fail when multiple apps share a similar bundle ID prefix (e.g., com.mycompany.app and com.mycompany.app.test)., it's related to this bug in new | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
|
||||||
|
|
||||||
| ###### Solution | ||||||
| The known and effective workaround is to explicitly force altool to use the correct app ID by passing the argument: ```--apple-id <app-apple-id>```. We’ve added support for an optional ```--altool-additional-arguments``` option to the app-store-connect publish action. This allows you to pass any additional CLI arguments directly to altool. You can also set this via the environment variable: ```APP_STORE_CONNECT_ALTOOL_ADDITIONAL_ARGUMENTS```. Your app's Apple ID can be found in AppStoreConnect > General > App Information > Apple ID | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. where to use the flag ?
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this section is unclear |
||||||
|
|
||||||
| {{< figure size="medium" src="../uploads/2025/altool-bug.png" caption="Environment variable for altool fix" >}} | ||||||
|
|
||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.