Xcode 27 creates a placeholder for the bundle identifier of a new project.
devplaceholder.$(PROJECT_UNIQUE_VALUE:identifier).$(PRODUCT_NAME:identifier)
I have two questions.
-
Is it enough to change the bundle id from the Signing & Capabilities panel or do we need to change it somewhere else?
-
What are Apple recommendations? Should we only replace the devplaceholder value and keep the unique value and product name, provide our won id but keep the product name, or replace everything with our own bundle ID?
Thanks
Is it enough to change the bundle id from the Signing & Capabilities panel … ?
Yes.
What are Apple recommendations?
The hard constraints are documented on the CFBundleIdentifier page.
Beyond that, it’s largely up to you. The general guideline is that you use an identifier that’s unlikely to collide with other developers. So if you’re working on the Waffle Varnishing app for Late Night Silly Software you might use com.latenightsillysoftware.waffle-varishing. But that’s just a guideline.
If you’re targeting the App Store, for any platform, then the Developer website will ensure that your bundle ID is unique.
If you’re directly distributing your app using Developer ID signing on the Mac then it’s possible to get collisions [1]. Hence the suggestion to use a format that’s unlikely to collide.
The components of the default bundle ID (devplaceholder, $(PROJECT_UNIQUE_VALUE:identifier), and $(PRODUCT_NAME:identifier)) only exist to give a unique and reasonable default value. They don’t make sense if you’re building a real product.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
[1] Unless your app is using restricted entitlements, in which case it needs a provisioning profile and that needs an App ID, which requires you to register your bundle ID with the Developer website.