Signing Arbitrary macOS Bundle Identifiers

If you’re shipping apps for both iOS and macOS, you’ve probably noticed that registering bundle identifiers with your developer team is necessary for iOS only.

Mandatory Identifier Registration for iOS

On iOS, Apple’s locked-down architecture means every app you distribute must have its bundle identifier registered in the Apple Developer portal. Because you cannot create a provisioning profile (required for signing and installation on devices) without first registering the identifier. This is fundamental to how iOS enforces its app security and distribution model.

Optional Identifier Registration for macOS

macOS is more open. If you’re distributing your app outside the Mac App Store, then you do not need to register the bundle identifier with your developer team. Apple’s code signing and notarization processes are based only on your Developer ID certificate, not on any pre-registered identifiers.

You can create and sign a macOS app with any bundle identifier, as long as it’s unique and follows Apple’s conventions. No need to interact with the Identifiers section of the Developer portal. Technically, you can also fake other third party apps on your system with this and confuse macOS about the local bundles.

Mac App Store

If you plan to distribute your macOS app in the Mac App Store you do need to register the bundle identifier. This is because the App Store review and submission process uses it for app management and uniquely identifying your submission.