Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Obtaining an App ID for iOS apps

Updated on February 23, 2022

Create a unique App ID in the Apple Developer Portal for the iOS certificate set that is required to generate an installation package for your iOS app.

Before you begin: Ensure that you have access to an Apple Developer Portal account.
When you configure an App ID, you create a unique bundle ID string that acts as an identifier for your app in Apple's ecosystem. Alternatively, you can create a wildcard bundle ID to identify a set of apps. The App ID also determines what types of Apple services your iOS app can support.
  1. Go to, and then sign in to your Apple Developer Portal account.
  2. On your account dashboard, click Certificates, Identifiers & Profiles.
  3. On the Certificates, Identifiers & Profiles page, in the category list on the left side of the screen, click Identifiers.
  4. In the Identifiers section, add a new identifier by clicking the plus icon.
  5. In the Register a New Identifier section, click App IDs, and then click Continue.
  6. In the Register an App ID section, in the Description field, enter a name that identifies your app in the Apple Developer Portal.
  7. Create a bundle ID for your App ID:
    Use the App ID for one specific app
    1. Next to the Bundle ID field, click Explicit.
    2. In the Bundle ID field, enter a unique string in the reverse-domain style.
      For example: com.example.expenses
    Use the App ID for multiple apps
    1. Next to the Bundle ID field, click Wildcard.
    2. In the Bundle ID field, enter a string that ends with an asterisk.
      For example: com.example.*
      You can use a wildcard App ID with any app whose bundle ID exactly matches all characters that precede the asterisk. The asterisk acts as a wildcard sign for at least one character in the remaining part of the bundle ID. For example, a com.example.* wildcard App ID matches both com.example.expenses and com.example.expenses.external bundle IDs.
    Important: Wildcard App IDs do not support all Apple capabilities. For example, push notifications are not available when you use a wildcard App ID.
  8. Optional: To add support for specific capabilities, in the Capabilities list, select the check box next to the capability that you want to support in your app.
    For example: To add support for push notifications, select the check box next to the push notifications capability. For more information, see Configuring push notifications for iOS apps.
  9. Click Continue.
  10. Optional: To ensure that your App ID remains valid in terms of future Apple guidelines and requirements, in the Deployment Details section, provide deployment details for your app:
    1. Click Yes, I have details on this app and plans for distribution.
    2. In the Estimated Distribution Volume list, select the volume range of target users for your app.
    3. In the Distribution Method category, select a check box next to at least one distribution method for your app.
    4. In the App Security Mechanisms category, select a check box next to at least one security method for your app.
    5. In the App Audience category, select a check box next to at least one target audience for your app.
    6. In the gray field at the bottom of the page, confirm the accuracy of the deployment details by selecting the check box.
  11. Click Continue.
  12. In the Confirm your App ID section, review the details of your App ID, and then click Register.
Result: Your new App ID is now available in the list of identifiers in your Apple Developer Portal account. When you upload a provisioning profile to an iOS certificate set in Pega Platform, the App ID that you associate with that profile is automatically added to the certificate set.

    Have a question? Get answers now.

    Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

    Did you find this content helpful?

    Want to help us improve this content?

    We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us