Ship identity fixes: display name "MetaWear", bundle ID of the existing store record#10
Merged
Conversation
The target/product is named MetaWearApp, and with no CFBundleDisplayName the home-screen label fell back to CFBundleName = $(PRODUCT_NAME) = "MetaWearApp". Set the display name explicitly — the App Store listing name lives in App Store Connect and was never affected, but the icon label ships in the binary. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The live MetaWear app (Apple ID 1547334547) ships as com.mbientlab.MetaWearApp — not com.mbientlab.MetaWear as this project assumed. App Store Connect routes uploads strictly by bundle ID, so the mismatch made Xcode try to CREATE a new app record (and collide with the existing "MetaWear" name) instead of attaching the build as the v10.0 update. The iCloud container stays iCloud.com.mbientlab.MetaWear: container identifiers are independent of bundle IDs and pinned explicitly in the entitlements, so the CloudKit Production schema already deployed there remains valid. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
lkasso
changed the title
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
1 participant
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.
Two fixes caught while preparing the v10.0 TestFlight upload, both about shipping identity:
CFBundleDisplayName, the icon label fell back toCFBundleName=$(PRODUCT_NAME)= "MetaWearApp". Now explicitly "MetaWear".com.mbientlab.MetaWearApp, notcom.mbientlab.MetaWearas this project assumed. App Store Connect routes uploads strictly by bundle ID, so the mismatch made Xcode try to create a new app record (colliding with the existing "MetaWear" name) instead of attaching the build as the v10.0 update. Verified against Apple's public lookup for id1547334547.The iCloud container stays
iCloud.com.mbientlab.MetaWear— container identifiers are independent of bundle IDs and pinned explicitly in the entitlements, so the CloudKit Production schema already deployed there remains valid.Distribution-signed ipa verified end-to-end: bundle
com.mbientlab.MetaWearApp, display name "MetaWear", 10.0 (1),aps-environment= production, iCloud env = Production, container intact,get-task-allow= false.🤖 Generated with Claude Code