My problem is the following: I created an application in XCode and I logged in with an account that is not enrolled in the Apple Developer Program. And the BundleId was automatically registered in that account. So now that we have the new developer account (Enrolled) it no longer lets me register the same bundleID. Because it tells me an error "cannot be registered to your development team because it is not available. Change your bundle identifier to a unique string to try again. And look in forums that the only solution is: Login to Apple Developer with the account that registered that bundleId Go to certificates Revoke the certificate But it is a free account. I do not see the option "Certificates" Please help!

Our app uploads successfully, but then I get the following message in an email from App Store Connect about an Invalid Code Signing Entitlements: "ITMS-90286: Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, value 'BFZC26JH2W.humansarehuman.blue2factor.macosbackground' for key 'com.apple.application-identifier' in 'Blue2Factor.app/Contents/Library/LoginItems/Blue2FactorBackground.app/Contents/MacOS/Blue2FactorBackground' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier ." The value for the key mentioned, BFZC26JH2W.humansarehuman.blue2factor.macosbackground, IS our TEAMID, followed by a dot, followed by the bundle identifier. The bundle is a target in our project, though it is not only target, and it is not the bundle ID that is identified as the BundleID on the App Store Connect - App Information page under the General Information heading. If anyone can point to what we're doing wrong, I would appreciated it. Thank you, Chris

We distribute an macOS app bundle with a main executable, a helper executable, a nested app bundle and an XPCService. myApp.app └── Contents ├── _CodeSignature │ └── CodeResources ├── embedded.provisionprofile ├── Info.plist ├── MacOS │ ├── myHelperApp.app │ │ └── Contents... │ ├── mainExecutable │ └── helperExecutable ├── PkgInfo └── XPCServices └── myXPCService.xpc └── Contents... Our mainExecutable requires FullDiskAccess and the helperExecutable requires Accessibility Access. Since this a product for enterprise customers, the TCC permissions usually get granted via a PPPC profile. What would be a good bundle identifier naming scheme for such a structure? com.example.myApp for the main app bundle/executable and com.example.myApp.helperExecutable etc. for all additional targets? When creating the PPPC profile, do I only refer to the bundle identifier of the main bundle com.example.myApp? If so, does that mean that every executable in that bundle has these privileges? At least this is what the manual approach would suggest, where the user can drag an entire app bundle to the privacy settings. The helperExecutable gets copied into the bundle during the build process. But when it is run from its Xcode scheme, it is run from the build directory, outside the final bundle. This requires the helper binary to be extra granted Accessibility permissions, at least during development. Is there a better way? Thanks (Quinn)!

Hi Forum, we developing an iOS SDK (framework) that will be used by our customer apps. The SDk will be hosted and distributed using cocoapod. The framework intern will use another vendor SDK / Framework and the vendor is asking bundle id to generate the license key. But as we are developing SDK and not an app, we do not have bundle id to share. How generally the licensing should be arranged in this cases (when a SDK is depends on another). Thanks, SD

Hello, I can't simulate my app because my Cpf bundle app is incorect someone know what is the problem about my cpf.

I have an application, released a few years back. The bundle ID starts with a digit, this used to be allowed. Now Xcode replaces the digit with a dash -, ie. 7K998EA8RN.org.nelsonmandela.quotes becomes -K998EA8RN.org.nelsonmandela.quotes Therefore on upload I get an error saying that the bundle ID does not match. If I end it the info manually and set the Bundle ID there, I can make it further down the process but still errors out as the application-identifier still becomes A8V6VR9K7C.-K998EA8RN.org.nelsonmandela.quotes the error returned is: ERROR ITMS-90046: "Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value 'A8V6VR9K7C.-K998EA8RN.org.nelsonmandela.quotes' for key 'application-identifier' in 'Payload/MandelaQuotes.app/MandelaQuotes' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier." Any idea on how to resolve this to push an update to this existing application? Thanks

What is to stop an attacker from creating a separate app with the bundle identifier of my app (minus the last component and with a fake last component), distributing it to users, then stealing the identifierForVendor? On Android there is this concept of ANDROID_ID that is shared across apps based on app signing key, which is much harder to steal and can be used for multiple apps on a team. On IOS the equivalent of sharing app signing key is to be in the same app group. Are there any plans to have an identifier that is shared across app groups? https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_application-groups