Skip to main content
Question

IOS Code error : 23. None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect


Forum|alt.badge.img+3

Hello, I have this error from RevenueCat: code: 23, message: There is an issue with your configuration. Check the underlying error for more details. There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect (or the StoreKit Configuration file if one is being used). More information: https://rev.cat/why-are-offerings-empty domain: RevenueCat.ErrorCode, userInfo: "readableErrorCode":"CONFIGURATION_ERROR","readable_error_code":"CONFIGURATION_ERROR","source_file":"RevenueCat/OfferingsManager.swift:237","source_function":"createErrorForEmptyResult(_:)","NSLocalizedDescription": There is an issue with your configuration. Check the underlying error for more details. There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect (or the StoreKit Configuration file if one is being used). More information: https://rev.cat/why-are-offerings-empty.

However, I can successfully import subscriptions from Apple Connect to RevenueCat. Everything seems to be set up correctly in the offering, which contains packages. Each package has two products, one from the Play Store and the other from the App Store. The entitlements correctly contain all 6 products. Everything works fine for Android, but for iOS, I get the above error. My iOS subscriptions are in the 'Ready to Submit' state.

I test on real device.

Thanks

 

26 replies

Forum|alt.badge.img+1
  • Helper
  • 3 replies
  • December 1, 2023

I think you should config StoreKit file and certificate… to test in simulator or real device associated with Xcode… 


kaitlin
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 342 replies
  • December 1, 2023

Hi @Mael,

The above advice is good - using the StoreKit config file can help to diagnose where the issue is stemming from. If you are able to test with a config file, then it shows us that your set up between Xcode and RevenueCat is working. That would narrow it down to the connection between XCode/RevenueCat and the App Store - the bundle id not matching, the product identifiers not matching. If you are able to import all of your subscriptions without issue and all your products are in the ready to submit state, then I’d check out your Paid Applications Agreement and your tax forms to make sure that they are all signed and nothing has quietly expired. 


Forum|alt.badge.img+1

Hello! I’m facing the same issue, I think I know what’s going on, but not sure how to resolve it. 

  • Everything works well in my debug builds (login, logout, fetching & purchasing), with a manually attached Storekit file and a sandbox signed in user.
  • However, when I run a “released version” on my phone, without a sandbox account, I get the same error as @Mael is seeing. 
  • Some additional info: This is the first version of my app (3.10) that has IAP. Last version submitted was 3.03 without IAP.
  • So, when i go to AppStoreConnect it seems like I still need to attach these  new subscriptions/products to my build and get approved by Apple. 

Question, am I seeing the error because these subscriptions have not yet been approved by Apple? Hence the app is unable to find these products when I run the release build on my device directly? If so, do I have to wait for apple to approve my app before i can test the “release version” on my device?

---

Here’s the error for reference:

“ERROR: 🍎‼️ Error fetching offerings - The operation couldn’t be completed. (RevenueCat.OfferingsManager.Error error 1.)

There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect (or the StoreKit Configuration file if one is being used). 

More information: https://rev.cat/why-are-offerings-empty

ERROR: 😿‼️ There is an issue with your configuration. Check the underlying error for more details. There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect (or the StoreKit Configuration file if one is being used). 

More information: https://rev.cat/why-are-offerings-empty”

 

Thanks a ton,

Siddhant


Forum|alt.badge.img+1
  • Helper
  • 3 replies
  • December 2, 2023

Did you create a duplicate of your scheme? because in sandbox you are using StoreKit file, but in TestFlight you should use the scheme where you are not using StoreKit and “cer” file… Also be sure you have complete agreements in AppleStore Connect and add bank account and tax information...


Forum|alt.badge.img+3
  • Member
  • 7 replies
  • March 12, 2024

I found the solution at the end of three days.

 

Every subscription was only active for Germany, and we kept getting this error when a device registered in the UK downloaded it from the app store.

 

If you can't solve it despite all instructions, make sure to check this situation as well.

make sure all countries are available.

 


Forum|alt.badge.img+2
  • New Member
  • 1 reply
  • September 10, 2024

Hi, guys! 

  Same error here.

 

  About your suggestions or questions:

  • "then I’d check out your Paid Applications Agreement and your tax forms to make sure that they are all signed":
    • I did that and all Paid Applications Agreement and tax forms are Ok, active or completed (Mexico)
  • "make sure all countries are available."
    • All available here. 
  • "am I seeing the error because these subscriptions have not yet been approved by Apple?"
    • No. I sent to approve and the reviewers expected all running ok. So, it is supposed to work because the testers were expecting that.

Some details:

  • Phisycal device: iPhone 14 Pro.
  • using Flutter PaywallView: 

PaywallView(

      offering: _offerings?.current!,

      displayCloseButton: true,

      onDismiss: () {...

  • Before I tested with manually configuration on RevenueCat. Now, I put the storeKit key and I got the same error. So I rule out the possibility of it being due to having or not having the storekit key configured

 

  Do you have some other idea what can I do to fix that? 

 

  I thank you in advance for your help


Forum|alt.badge.img+1
  • New Member
  • 1 reply
  • September 17, 2024

Same issue, since iOS 18.0


Forum|alt.badge.img

I am also having this issue . but it was working fine earlier , 

but after my apple developer license expired and i renewed .. after that i am getting this error .. any idea


Forum|alt.badge.img+1
  • New Member
  • 1 reply
  • October 15, 2024

Hello, same issue here, only these OS versions seem to be affected:

 

 


Forum|alt.badge.img

Any idea about how to resolve this issue ?


kaitlin
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 342 replies
  • October 21, 2024

Hey @ajith-joseph-6ca589,

There’s a lot of great advice in the above thread, but you can also check out this guide of common causes for this issue: 

Another important thing to note - if the issue does turn out to be the Paid Applications Agreement or an unsigned/expired tax form, it can take up to 24 hours for the error to clear even after the Agreements or form are signed. This is a limitation on Apple’s side, similar to new product propagation time. 


@kaitlin I’m having the same issue. Didn’t touch my configuration in any capacity, has been working fine for a year, and now suddenly SOME customers are telling me they can’t start a trial. I think the issue must be something on the RevenueCat side.

 

(side note: how do I change my username? Mis-clicked and now I’m stuck with this one :D)


Forum|alt.badge.img
ajith-joseph-6ca589 wrote:

Any idea about how to resolve this issue ?

I resolved my issue , after i renew my apple developer license , one of my license agreement was expired , nd i havent noticed that. i accept that , after few hours it was fixed automatically


Dev agreement signed three days ago, issue persists. Touched nothing in the configuration, which has been working fine for years. Am out of things to try, and have had no trial starts during the past three days (as opposed to some during the days before, and some users saying they’re getting an error) which means that it is now affecting ALL users.


FOUND THE ISSUE: There seems to be a bug in the latest version of the RC package. Downgraded it and now it works.


Forum|alt.badge.img+2
tina-aspiala-d6eace wrote:

FOUND THE ISSUE: There seems to be a bug in the latest version of the RC package. Downgraded it and now it works.

Can you please tell us which RC package version that is working for you? I am having same issue with ios 18.1 and this error appeared suddenly without changing anything  


Forum|alt.badge.img

I am getting the same error but on Android only!  Is this really a version issue? 


kaitlin
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 342 replies
  • December 3, 2024

Hey all,

This error really wouldn’t be tied to a package version - it’s likely a coincidence that it cleared at the same time. It signifies a configuration issue. If the error appeared suddenly without any changes on your end, check on your banking information and tax forms with the stores, ensuring that nothing has expired or needs to be signed. On Apple’s end, the Paid Application Agreement can also expire without alerting you. For all of these things, there can be a period between fixing it and when the error will clear - we usually recommend allowing 24 hours but we’ve also seen longer. 

Some additional things to check on Google’s end are that your test track has been approved and published by Google, and that the user you’re testing with is an opted in licensed test user. 


Forum|alt.badge.img+1

I have same issue. There is no problem on my device and simulator. But Apple Tester takes this error on review. So my app rejected.

"Error 23: There is an issue with your configuration. Check the underlying error for more details."


I have the exact same issue as trevor-beaton.


I have the same issue; this error is showing in production. Although my app has been approved by Apple.


  • New Member
  • 1 reply
  • December 23, 2024

Same issue. ​@kaitlin Can you please have the team prioritize this issue? Thank you.


Forum|alt.badge.img+1
  • New Member
  • 1 reply
  • December 23, 2024

Same issue. My app has been rejected because of this


jeffrey_bunn
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 162 replies
  • January 3, 2025

Hi everyone - thanks for sharing your experience with this. Regarding this happening in App Review, I wanted share more on the different environments Apple uses.

When testing on your own device, the “Sandbox” environment is used, which is (unfortunately) notoriously flaky, with regular outages and, sometimes, purchases can get hung up in their system.

In TestFlight and in App Review, the “Production Sandbox” environment is used, but we find this environment just as flaky as the “Sandbox” environment. This is one reason why you’re able to test without issues on your device, yet App Review can run into this issue. As long as you’ve carefully reviewed our empty offerings document and signed all agreements (more on this below), you can have confidence that this is an environment issue and resubmit.

In production, the “Production” environment is used, which is (thankfully) very stable. We don’t tend to see this issue in production, so if you are seeing it, please reach out to us so we can investigate (cc ​@abdullah-naim-133e52). 

Regarding App Store Connect agreements, it’s important to ensure everything is signed. This is also the case for Apple Developer agreements (separate from App Store Connect). Recently, I’ve also noticed that this issue may occur even if some of the Banking information hasn’t been completed, so please review this as well.

Echoing ​@kaitlin, there may also be a 24 hour+ period between executing all agreements and the error resolving. 


Forum|alt.badge.img+1
  • New Member
  • 1 reply
  • January 8, 2025

I’m going to echo some other sentiment here that this error message is very unclear with respect to the root cause and the diagnostic approach is not effective. I’ve run into this issue now twice, with two separate apps, and I’m not doing anything particularly strange, so I’d assume that whatever is happening is impacting basically every implementation.

I have several products, all waiting for review, and all of my App Store agreements are up to date. I’m also using a StoreKit file to test locally. I’m seeing the “Error 23” error regardless (using the StoreKit file in simulator, non-StoreKit on device, etc.).

Not sure what else to do other than wait and see if it resolves…

Here is the error I see in logs, in case it helps (for the record, the linked document did not help resolve the issue for me):

ERROR: 😿‼️ There is an issue with your configuration. Check the underlying error for more details. There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect (or the StoreKit Configuration file if one is being used). 
More information: https://rev.cat/why-are-offerings-empty

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings