Skip to main content
Solved

Apple App Store - bundle id failed to link to in-app purchase key

  • February 22, 2026
  • 9 replies
  • 100 views
D
Forum|alt.badge.img+1

I have two bundle ids in my App Store Connect account: com.example.prod and com.example.dev.

In RevenueCat if I use com.example.prod in RevenueCat App Configuration, the validation under ”P8 key file from App Store Connect” went through. However, if I use com.example.dev, I’ve got “The key is not valid or is not compatible with the Bundle ID of your app.”

I believe the in-app purchase key (.p8 file) can be used for any bundle ids under the same App Store Connect account. Why in RevenueCat, one works while the other doesn’t.

Best answer by Tarek

Hey David,

In a nutshell, to keep it simple, your bundle id should be the same across three places:

  • In your app information on App Store Connect (this is the reference, you can't change it without recreating the app, so copy it and make sure you use it in the following places)
  • In your RevenueCat dashboard, under Apps & providers, as an Apple app configuration
  • In your code, for instance your Xcode project

Once you have those three in sync and exactly the same, your RevenueCat SDK will use your app bundle identifier in the code to make requests to Apple's StoreKit, and your RevenueCat dashboard will sync with the App Store Connect API using what you have in Apps & providers.

And it will work fine, I just tested your configuration in a sample project, your default (current in code) offering is now valid and products load properly.

Best regards,

    9 replies

    cam
    Forum|alt.badge.img+2
    • cam
    • Helper
    • February 23, 2026

    Hi, 

     

    The same key should work for all apps belonging to the same account. Could it be that you have missing agreements to sign for “com.example.dev”?

     

    Cam

      D
      Forum|alt.badge.img+1
      • david-0a0eaa
      • Author
      • Member
      • February 23, 2026

      Thanks, Cam, for your reply. What agreements are you referring to?

      I’ve double-checked that the Paid Applications Agreement in Business is active, and the bank account is active as well (although I think this agreement is account based). There are no pending agreements or notifications under the account.

       

      I should have included following in my original post because it’s more important: Even with the working com.example.prod bundle ID, the app still throws exception: “None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect.” I’ve been struggling with this issue for days and have ruled out every step in the guide - www.revenuecat.com/docs/offerings/troubleshooting-offerings. I feel very frustrated that it has to be so complicated and so hard to fix.

        Tarek
        RevenueCat Staff
        Forum|alt.badge.img+3
        • Tarek
        • RevenueCat Staff
        • February 23, 2026

        Hey ​@david-0a0eaa,

         

        Thank you for reaching out. I'm Tarek, from the support team, and I'll happily help you figure this out.

         

        You are dealing with two different issues:

        1. Your credentials not being validated with your "dev" bundle ID
        2. Your products being empty even with your valid "prod" bundle ID

         

        Regarding the first issue, if you want to have a dev version and a prod version of the same app, you would need indeed to create two different apps in App Store Connect, each one with its own bundle ID (by the way, the bundle ID is case sensitive, this is a common issue).

         

        I checked what we could fetch from your App Store Connect account, and the bundle ID is different from what you described. Please double check the bundle ID you're entering in the app configuration.

         

        However, I want to draw your attention to the fact that you would also need to create a set of subscriptions for the dev version of your app.

         

        If you tell me what you are trying to achieve with those two versions in App Store Connect, I can help you and suggest you a sensible RevenueCat configuration for this.

         

        Regarding the second issue, you're seeing this error because your default offering, doesn't have any Apple products in the associated packages, but only packages from the Test Store so far. Feel free to edit your package and associated the right products, then they will show properly in your app.

         

        Do not hesitate to reach back if I can help you further!

         

        Best regards,

        D
        Forum|alt.badge.img+1
        • david-0a0eaa
        • Author
        • Member
        • February 23, 2026

        Thanks, Tarek. It’s nice to have RevenueCat’s support so quickly.

        Yes, there are indeed two issues here. So, I have submitted both the IAP key and App Store Connect API key. The first issue is you can fetch the products from my App Store Connect account with my prod bundle id (which you have verified) and not with dev bundle id (my bundle ids are in lower case). I can create a separate App in my App Store Connect for dev only. My question is how does RevenueCat know to fetch with prod bundle id instead of dev bundle id (I’m not referring to inputing the bundle id in RevenueCat dashboard, not sure if I’m clear on my question)? Except from the name difference, they should be the same from RevenueCat’s view?

         

        The second issue is more important and critical actually. The products in the default offering are from test store. My real products are in a separate offering xxx_prod and this is the offering I’m using (I’m also using the RevenueCat API key for this offering). I will give it a try to put all my products in the default offering though. 

        D
        Forum|alt.badge.img+1
        • david-0a0eaa
        • Author
        • Member
        • February 23, 2026

        I moved real products to default offering and still get this error “None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect”
         

        D
        Forum|alt.badge.img+1
        • david-0a0eaa
        • Author
        • Member
        • February 24, 2026

        Hi — just bumping this thread to see if RevenueCat support team could help. Thanks in advance!

        Tarek
        RevenueCat Staff
        Forum|alt.badge.img+3
        • Tarek
        • RevenueCat Staff
        • Answer
        • February 24, 2026

        Hey David,

        In a nutshell, to keep it simple, your bundle id should be the same across three places:

        • In your app information on App Store Connect (this is the reference, you can't change it without recreating the app, so copy it and make sure you use it in the following places)
        • In your RevenueCat dashboard, under Apps & providers, as an Apple app configuration
        • In your code, for instance your Xcode project

        Once you have those three in sync and exactly the same, your RevenueCat SDK will use your app bundle identifier in the code to make requests to Apple's StoreKit, and your RevenueCat dashboard will sync with the App Store Connect API using what you have in Apps & providers.

        And it will work fine, I just tested your configuration in a sample project, your default (current in code) offering is now valid and products load properly.

        Best regards,

        D
        Forum|alt.badge.img+1
        • david-0a0eaa
        • Author
        • Member
        • February 28, 2026

        It’s working now. What I did was copy and paste the bundle id to the project file and RevenueCat again. Then copy and paste the RevenueCat key to the project again. Then create the products in the “default” offering and wait12 hours before testing. Not sure which step actually resolved the issue, and it might sound non-sense, but it works. I guess there may be an unnoticed character error somewhere, or a caching issue.

        Lastly, I’d like to thank the RevenueCat Support team for their lightning-fast help.

          Tarek
          RevenueCat Staff
          Forum|alt.badge.img+3
          • Tarek
          • RevenueCat Staff
          • March 1, 2026

          Happy to hear it's fixed ​@david-0a0eaa!

          Thank you David for your kind words, it means a lot.

          All the best,

          Terms & ConditionsCookie settingsAccessibility statement