The mentioned way of setting up complications does not work. We can't create the identifier according to the guideline mentioned in the WWDC session.
https://developer.apple.com/videos/play/wwdc2020/10049/?time=1021
Timestamp: 17:04
Error:
An attribute in the provided entity has invalid value
An App ID with Identifier '.watchkitapp.complication' is not available.
Please enter a different string.
To clarify - the non masked identifier is not used on another property inside our dev program.
Without creating the identifier our tests result in not working push notifications.
Error message while testing: discarded as application was not registered.
Is the way mentioned in the WWDC session still valid?
BR
Posts under Bundle ID tag
44 Posts
Sort by:
Post
Replies
Boosts
Views
Activity
Hi, I am currently working on an App Transfer from Company A to Company B but can't find any documentation about what happens to existing Siri Shortcuts working via App Extension intents.
I have separated the rest of the post in 2 sections: one what summarizes my current understanding and the other with some questions and hypotheses. It would be great to have either someone from Apple to answer that, or someone else share their experience and possibly some documentation that I might have missed.
To my understanding, when a new Shortcut is created, it stores the BundleID of the App and of the App Extension to find the application that will execute it afterwards. If I uninstall the App, I can see a message in the Shortcut app that says "This action requires APPNAME but it may not be installed", but I know that after transferring the app the BundleID doesn't change completely, only the team part does. However, it is not possible to test that as this change cannot be done in xCode as far as I know.
Another part that seems to play a role here is the info.plist file, but in my situation, there are no entries related to the BundleID.
All that being said, I am wondering:
Is it possible to perform an app transfer and keep previously created shortcuts working?
Is it possible to test this kind of things without having to perform a transfer? I haven't found a way to change the team part of the Bundle ID
Is there a place in the documentation that takes care of those things in depth?
Hello,
I’m facing an issue with enabling In-App Purchases (IAP) for my iOS app, and it’s causing provisioning errors during the build process.
Issue:
• In Apple Developer Portal → Certificates, Identifiers & Profiles, the In-App Purchase capability is checked but grayed out, so I can’t modify it.
• In Xcode, under Signing & Capabilities, I don’t see In-App Purchase listed.
• When trying to build, I get the following error:
Provisioning profile “BillionMines_Dev_Profile” doesn’t include the com.apple.developer.in-app-purchase entitlement.
• Automatic signing in Xcode fails with:
Xcode failed to provision this target.
What I Have Tried:
1. Verified that my App ID is explicitly defined (not a wildcard ID).
2. Regenerated and downloaded a new Provisioning Profile, ensuring it matches my app.
3. Confirmed that In-App Purchase is enabled in App Store Connect under Features.
4. Cleaned the build folder and restarted Xcode.
5. Manually added com.apple.developer.in-app-purchase to my .entitlements file.
Questions:
• Why is the In-App Purchase option grayed out in Certificates, Identifiers & Profiles?
• How can I ensure my provisioning profile includes the com.apple.developer.in-app-purchase entitlement?
• Are there additional steps required to fully activate In-App Purchases?
Any help would be greatly appreciated!
Thanks in advance.
Hello everyone,
I’m currently developing an Electron application, and I’m trying to properly sign and notarize it for macOS. The notarization process itself seems to complete successfully—the file is accepted without issues. However, when I attempt to staple the notarization ticket to the executable, I consistently get Error 65 with TheStableAndValidateActionFailed.
The issue is puzzling because the executable does not change at any point during the process. After facing this issue multiple times in my own project, I decided to test it on a more controlled setup. I followed the steps from this https://www.youtube.com/watch?v=hYBLfjT57hU and the instructions from this macos-code-signing-example which have previously worked for others. Yet, even with this setup, I still get the same Error 65.
Below, I have attached the verbose logs for reference. I’m trying to understand what could be causing this issue—whether it’s related to certificates, the signing process, or something else entirely.
Has anyone encountered a similar problem, and if so, how did you resolve it? Any insights would be greatly appreciated!
We've recently transferred one of our existing Production apps to a new centralized store in Apple, and the Bundle ID has changed. What's the customer experience for those with the old app? Are they able to upgrade in place, are they notified there's a new build, or do they need to first delete the old app and then search and download the new one?
Steps:
I created a bundle ID.
Created an app and used the above created bundle ID
Remove the app
Tried to create a new app with the same bundle ID as it is still available and I did not delete it
Issue: This Bundle ID is not shown in the dropdown when creating the new app
Hi everyone,
I am doing my app playground, when I change the development team or try to clear it, this bug happend? So I wonder do I have to remove it when I submit my work or just leave it there.
Signing for "myapp" requires a development team. Select a development team in the Signing & Capabilities editor.
After changing the bundle identifier of my app, I’ve encountered several issues that I can’t seem to resolve, even though I’ve followed all the necessary steps. The app with the previous identifier was live on Testflight, and working perfectly fine, but now I’m facing the following problems:
WeatherKit Authentication Issue
WeatherKit has stopped working, and I’m getting authentication errors. I’ve updated the app in the Developer Portal to reflect the new bundle ID, but it still doesn’t authenticate properly.
Xcode Cloud Configuration Issue:
Xcode is asking me to set up Xcode Cloud again, which I understand is expected after a bundle ID change. However, during the setup process, it fails to recognize my remote repository, even though the repository is correctly added and visible under the Source Control tab.
TestFlight Internal Testing Issue:
I manually uploaded a build to TestFlight, but internal testers cannot use it because the invitation appears as invalid. This wasn’t an issue with the app’s previous identifier.
It seems like the bundle ID change has caused some fundamental issues that I can’t resolve despite following all the usual instructions. Has anyone experienced this before or knows how to resolve these problems?
I'm using the latest Xcode 16.2 on Mac OS Sequoia 15.2
I have the same problem as this question: https://developer.apple.com/forums/thread/757605
"That indicates you’re using a unique App ID prefix. This is a legacy feature that’s not supported on macOS."
Mine is a macOS App distributed in 2021, that now needs an update.
It has always been under Xcode automatically managed signing with a Team. (Still have the project files from 2021: automatic)
Now validating a new version gives me that error :
Invalid Provisioning Profile. The provisioning profile included in the bundle com.*** [***.pkg/Payload/***.app] is invalid. [Invalid 'com.apple.application-identifier' entitlement value.] For more information, visit the macOS Developer Portal. (ID: ***)
And even re-validating the old archive from 2021 gives me this error.
I have looked at my Apple Id's on "Certificates, Identifiers & Profiles", and I can indeed see that this app has an "App ID Prefix" that is not my Team, but something I don't recognise.
I can not make a new App ID Configuration for the bundle id I have been using: "An App ID with Identifier 'com..appname' is not available. Please enter a different string."
Removing the existing App ID Config does not work either: The App ID '.com..' appears to be in use by the App Store, so it can not be removed at this time.
So, I'm a bit stuck. (Help!)
I am encountering an issue when trying to register the bundle ID com.cbm.qmobile for my app. I’ve tried both adding it directly in Xcode and creating it manually in the Apple Developer portal, but I am unable to proceed in either case.
When I attempt to register the bundle ID in Xcode, I receive the following error: "The app identifier 'com.cbm.qmobile' cannot be registered to your development team because it is not available. Change your bundle identifier to a unique string to try again."
When I try to create the bundle ID manually on the Apple Developer website, I get this error: "An attribute in the provided entity has invalid value. An App ID with Identifier 'com.cbm.qmobile' is not available. Please enter a different string."
I have verified that my Apple Developer Program membership is active and that I am using the correct account. I also checked to ensure the bundle ID format complies with Apple’s guidelines.
This bundle ID is crucial for my app, and I would appreciate your assistance in resolving this issue.
Can I change the bundle identifier for an app that I have pushed to TestFlight beta testing but have not released a single build to the App Store yet?
I hover over the bundle identifier in the App Information section of the App Store Connect Apps page, but I do not currently see an option to edit it.
Recent Incident with SDKAnalytics Version 11.11.4
We recently released version 11.11.4 of SDKAnalytics for use in the SuperApp. This update introduced several significant changes since the last generated version, 11.11.0. The previous version's primary change was the migration of the integration pipeline and its identifier from OQ6 to FW6. Additionally, we performed refactoring and adjustments to the project's configurations.
In SDKAnalytics, we use XcodeGen to simplify project setup and minimize conflicts. We also rely on CocoaPods to create and manage our Pods/Frameworks.
The SuperApp, where SDKAnalytics is implemented, operates as a centralized ecosystem. Its products and user journeys are segregated into Pods/Frameworks, distributed across multiple repositories, following a multi-repo structure. Currently, the app includes over 300 Pods.
Starting from version 11.11.1 of our SDK, we implemented some important project changes. However, when we released version 11.11.4, which included a new feature for the SuperApp, we encountered a critical issue.
Incident Overview
All SDKs implemented in the SuperApp have their loading times monitored. After updating SDKAnalytics from version 11.11.0 to 11.11.4, the loading time spiked from 200 ms to 3000 ms. Faced with this significant impact, we launched a task force to investigate and resolve the issue.
Investigation and Diagnosis
After several days of investigation, we carefully reviewed the numerous pull requests merged between versions 11.11.0 and 11.11.4. As a strategy, we reverted the project.yml configurations from version 11.11.4 to match those of version 11.11.0. This rollback resolved the loading time issue, indicating that the problem stemmed from the project's configuration.
Upon deeper analysis, we identified the culprit: a single line of configuration. The Bundle ID for the SuperApp follows the pattern com.companyname.enterprise. However, in version 11.11.4, SDKAnalytics adopted a new Bundle ID format: com.companyname.SDKAnalytics. This change directly impacted the SDKAnalytics loading time when implemented in the SuperApp.
Solution
To resolve the issue, we reverted this configuration. We modified the Bundle ID for SDKAnalytics to br.com.SDKAnalytics, removing the com.companyname prefix. After this change, the loading time returned to normal.
Reflection
The lingering question remains: What is the logical explanation for this discrepancy in loading time caused by the Bundle ID configuration? This behavior is unexpected, and we plan to investigate further to understand the underlying technical reasons.
Hi Team,
How can I share info beetween two differnt App. What king of approach should I use. Thanks in advance.
In my case I whant to share a token or an string like "GM-8090"
How can I modify bundleID of an app after building ipa file?
I try to modify the bundle id in my app by :
unzip ipa
modify bundle id in info.plist within app
resign app with entitlements
4.zip ipa
but ipa appeared to not be able to install on iphone
is that any way to modify bundle id after building ipa file?
Thanks for your Support
Hello,
I had app written in React Native using Expo.
Now, I cleared up Expo from project, created new project, moved old source file to new project. Everything works fine.
Now I want to publish new project using old bundle id to overwrite existing app, but I can't.
What is problem?
Is not permitted to do that?
Maybe I need to provide something additionally?
Thank you for helping.
I'm integrating AdMob rewarded interstitial ads into my live iOS app using CocoaPods and package dependency management. The ads are working fine when I use the bundle identifier com.CreativeCub.ProgrammingHu, but when I use the correct identifier com.CreativeCub.ProgrammingHub, the ads stop working.
Here’s what I’ve tried:
Verified that the bundle identifier matches across Xcode and AdMob.
Double-checked the App ID and Ad Unit ID in the AdMob dashboard for com.CreativeCub.ProgrammingHub.
Reinstalled the AdMob SDK using CocoaPods.
Attempted to integrate AdMob using Swift Package Manager.
Created a test project to rule out potential issues with my existing project.
Despite these steps, ads only work when I use the shortened bundle identifier (com.CreativeCub.ProgrammingHu), which is not the correct one.
Contacted Google admob support for the same but did not worked
Tried running in different MacBook system
Our desktop app for macos will be released in 2 channels
appstore
dmg package on our official website for users to download and install
Now when we debug with passkey, we find that the package name of the appstore can normally arouse passkey, but the package name of the non-App Store can not arouse the passkey interface
I need your help. Thank you
Hi,
When I try to create an App ID for my app, I get the following message:
"An App ID with Identifier '' is not available. Please enter a different string.
I have not manually created an App ID under my team with this bundle identifier. I have 'Automatic Signing' checked in Xcode but am unable to upload or register an app with the same bundler Identifier through Xcode as well. I am not a member of any other team so this bundle identifier should be unique and should not have been used before.
Would appreciate any help.
Thanks.
I am currently developing an iOS app with a new feature that utilizes Quick Start for data migration between devices. We are testing this in a test environment using an app distributed via TestFlight.
However, we are encountering an issue where the app installed on the pre-migration device (distributed via TestFlight) does not transfer to the post-migration device. Could this issue be related to the fact that the app was distributed via TestFlight? Is there any restriction where only apps released via the App Store can be migrated using Quick Start?
We would appreciate it if you could provide some insights into the cause of this issue and any alternative testing methods.
Good day. As part of a business unit separation, we are required to have our product with a different name, bundle IDs and certificates than our current configuration.
The product contains network extensions and requires Full Disk Access. We distribute this product to our customers who either support MDM or not.
I know from previous experience that a product can be transferred to a different account, which is something we could do only for some parts of our product (only a couple of Bundle IDs).
My question is what's the best way to do this. I can imagine that having a scripted scenario where the other business unit's product is removed from customers and ours is installed, in a different folder.
The main issue I can foresee is that because our architecture uses several network extensions that are installed as plugins (bad design I know), we would be asking the users for authorisation, again, to use those extensions, plus full disk access.
What options do I have?