Our Appclip is not included in our build when we upload to App Store Connect the archive we exported from XCode. The problem may come from our bundle identifier : in XCode, in the “signing & capabilities” settings, we have 3 errors when choosing as our Appclip bundle identifier the same identifier as the app (companyName.AppNamepart1.AppNamepart2), followed by the .Clip suffix. Here are the errors we get : _Communication with Apple failed. App ID configuration error: This app ID does not include the parent app ID. To continue, register a new identifier with the parent app ID as the prefix. Provisioning profile "iOS Team Provisioning Profile: *" doesn't support the On Demand Install Capable capability. Provisioning profile "iOS Team Provisioning Profile: *" doesn't include the com.apple.developer.on-demand-install-capable and com.apple.developer.parent-application-identifiers entitlements._ We have also tried registering a new bundle identifier on the App Store Connect on this url : https://developer.apple.com/account/resources/identifiers/bundleId/add/ but we cannot seem to be able to type anything in the “Identifier” input field. Do you have any lead on how to solve our issue?

My app is on the App Store. Now I would like to publish a "lite" version of my app. Its name could be something like "MyApp lite", it has only a reduced set of features. I think it would be accepted on the reviewal process because it is not unusual that two similar apps are in the App Stores, one having just the main features and the other being complete. Let's say they are identified by com.myappdomain.app and com.myappdomain.app.lite 1-Is it possible to publish such a "lite" app along the main one (different pricing or business model)? 2-Can its name be like "MyApp lite" (or similar wording)? 3-Can they have the same app icon? 4-Can they be installed at the same time on a device? 5-The two apps are compatible with a special data type, importing, exporting, and launching with files with a special registered file extension. This is from the info.plist <key>CFBundleDocumentTypes</key> ... <key>CFBundleTypeName</key> <string>com.myappdomain.mydatatype</string> <key>NSUbiquitousDocumentUserActivityType</key> <string>$(PRODUCT_BUNDLE_IDENTIFIER).mydatatype</string> ... <key>UTExportedTypeDeclarations</key> ... <key>UTImportedTypeDeclarations</key> ... <key>CFBundleDocumentTypes</key> ... <key>CFBundleTypeName</key> <string>com.myappdomain.mydatatype</string> <key>NSUbiquitousDocumentUserActivityType</key> <string>$(PRODUCT_BUNDLE_IDENTIFIER).mydatatype</string> ... I changed the bundle identifier in certain places for the new project (the original code, stripped of many features) but I see that there is also $(PRODUCT_BUNDLE_IDENTIFIER).mydatatype for NSUbiquitousDocumentUserActivityType that changes for the two apps, while the other plist settings are the same. Is it right? Should the two apps have the same NSUbiquitousDocumentUserActivityType value instead? Thanks in advance

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

I am getting following error every time I'm validating my bundle. App Store Connect Operation Error. The bundle uses a bundle name or display name that is already taken. No matter I changed the Display Name or the Bundle Identifier, it always gives this error when I try to validate the archive from Organizer. Is there any limitation, for a personal developer to submit apps or creating Bundle IDs in developer portal? As an example, my most Bundle IDs created using following format. com.mypersonaldomain.applicationname That means most of my bundle IDs having "com.mypersonaldomain" part is common. Also, since this issue, now I have unwanted Bundle IDs in my developer portal which I cannot removed. Is there any way to get removed those as well?