I'm trying to let a few teammates build and run my app on their own devices, and I'd like to understand the correct approach for our situation.
Setup
- We are a small team. Each of us uses a free personal Apple Developer team (individual Apple IDs, no paid membership yet).
- The app (an iOS app with a Watch app and a WidgetKit extension) uses App Groups and HealthKit.
- Bundle IDs: com.example.MyApp, com.example.MyApp.watchkitapp, com.example.MyApp.Widget. App Group: group.example.MyApp.
It builds fine for me. When a teammate opens the project and tries to run on device, they get:
Failed Registering Bundle Identifier
The app identifier "com.example.MyApp" cannot be registered to your development team because it is not available. Change your bundle dentifier to a unique string to try again.
What I've observed
- My other apps that have no entitlements build fine for every teammate. Looking at their embedded profiles, those sign with a wildcard profile (TEAMID.*).
- This app signs with an explicit profile (TEAMID.com.example.MyApp).
- If a teammate removes HealthKit and App Groups from all targets, the app builds for them under their own team using the same bundle ID.
My understanding (please correct me) App Groups and HealthKit require an explicit App ID, which can only be registered to one team. Since I registered com.example.MyApp first, no other personal team can register the same explicit App ID hence the error.
My questions
- Is that understanding correct — that an entitled (explicit) App ID can only ever belong to a single team?
- Is there any supported way to keep the same bundle identifier and keep App Groups + HealthKit while teammates build under their own separate personal teams? Or is moving to an Organization account (everyone as members of one shared team) the only way to share an entitled bundle ID across multiple developers?
- For free personal-team development, is the recommended pattern to give each developer a unique bundle ID + App Group (e.g. via per-developer .xcconfig), keeping entitlements intact?
Just want to confirm I'm choosing the right approach before committing to it. Thanks!
Your understanding is correct. In response to your questions:
- Yes, an explicit App ID is registered to a single team.
This is a fundamental scoping rule of the Apple Developer Program. App IDs (including those with associated capabilities like App Groups and HealthKit) are registered within a specific team's portal namespace. Personal teams are isolated from each other; each personal team has its own namespace.
App Groups specifically are documented as scoped to a single team: "An app group allows multiple apps developed by the same team to access one or more shared containers."
https://developer.apple.com/documentation/Xcode/configuring-app-groups
- There is no documented mechanism to share an explicit App ID across separate personal teams.
Each personal team has its own portal namespace, and an explicit App ID (with its associated App Group identifier) belongs to one team.
- An Apple Developer Program organization team is the documented path for collaborative development on apps with team-scoped entitlements.
In an organization team, multiple developers are added as team members and share the same App IDs, App Groups, and provisioning profiles. This is how Apple Developer Program memberships are structured for team-based development.
For details on Apple Developer Program enrollment:
https://developer.apple.com/support/compare-memberships/
- For continuing with free personal teams, your proposed pattern is a reasonable workaround.
Each developer using their own personal team needs their own bundle ID and their own App Group identifier. A common pattern is to manage per-developer bundle IDs in .xcconfig files. This keeps source code consistent while letting each developer's local install use their own identifiers.
With each developer using their own App Group, integration testing of App Group-based interactions can't validate against a shared App Group identifier. That validation requires a shared Apple Developer Program team.