Context
After the companion iOS TestFlight upload path was repaired, App Store Connect still has several old or invalid provisioning profiles from earlier bundle-id experiments.
Current successful path:
- iOS companion app bundle:
com.shinycomputers.contextpanel
- iOS companion widget bundle:
com.shinycomputers.contextpanel.widget
- New widget profile used for the fixed upload:
ZRNF2CRN39 / UUID 6a6b6569-4843-4567-adcf-2ad5bdfca065
- iOS TestFlight upload succeeded for
1.0.30 (202606171523)
- TestFlight group
OG already had all-build access
Cleanup Candidates
Do not delete anything until the new TestFlight build is verified on device.
Likely stale / obsolete profiles:
- old companion app profile for
com.shinycomputers.contextpanel.companion
- old companion widget profile for
com.shinycomputers.contextpanel.companion.widget
- invalid current widget profiles generated before the widget App ID had the iCloud container assigned
Known examples from the pre-cleanup inventory:
D7HK62749P / UUID c668e5c1-c3ce-4684-8548-0d9994f0ba6c old companion app profile, active at the time of inventory
U4LUVB882M / UUID 9ee9b47c-257e-44b8-8c55-e9daaa4c22e1 old companion widget profile, active at the time of inventory
6JY3TZN2GQ / UUID 5952eb09-3bb4-41dc-b070-56f4420aeac3 current widget profile, invalid after portal changes
PA4RBA4GFV / UUID a830b7e0-9735-4f8c-bb16-e096663e923a current widget profile, invalid after portal changes
Acceptance Criteria
- Confirm the new iOS/iPadOS TestFlight build installs and reads iCloud/widget data correctly.
- Re-inventory App Store Connect profiles before deleting anything.
- Remove or retire profiles that are definitely stale, invalid, or tied to abandoned
.companion bundle IDs.
- Keep profiles still needed for macOS release/TestFlight and current iOS companion upload paths.
- Update release/docs/planning notes only if cleanup changes the expected profile names, IDs, or operator workflow.
Non-goals
- Do not delete App IDs until we are sure no TestFlight/App Store history or migration path depends on them.
- Do not alter source entitlements or upload-script preflights as part of profile cleanup.
- Do not run a full release; this is ASC hygiene only.
Context
After the companion iOS TestFlight upload path was repaired, App Store Connect still has several old or invalid provisioning profiles from earlier bundle-id experiments.
Current successful path:
com.shinycomputers.contextpanelcom.shinycomputers.contextpanel.widgetZRNF2CRN39/ UUID6a6b6569-4843-4567-adcf-2ad5bdfca0651.0.30 (202606171523)OGalready had all-build accessCleanup Candidates
Do not delete anything until the new TestFlight build is verified on device.
Likely stale / obsolete profiles:
com.shinycomputers.contextpanel.companioncom.shinycomputers.contextpanel.companion.widgetKnown examples from the pre-cleanup inventory:
D7HK62749P/ UUIDc668e5c1-c3ce-4684-8548-0d9994f0ba6cold companion app profile, active at the time of inventoryU4LUVB882M/ UUID9ee9b47c-257e-44b8-8c55-e9daaa4c22e1old companion widget profile, active at the time of inventory6JY3TZN2GQ/ UUID5952eb09-3bb4-41dc-b070-56f4420aeac3current widget profile, invalid after portal changesPA4RBA4GFV/ UUIDa830b7e0-9735-4f8c-bb16-e096663e923acurrent widget profile, invalid after portal changesAcceptance Criteria
.companionbundle IDs.Non-goals