Skip to main content
  • Community
  • Get Help
  • General Questions
  • 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)
Error Domain=RevenueCat.ErrorCode Code=23 "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" UserInfo={source_function=createErrorForEmptyResult(_:), source_file=RevenueCat/OfferingsManager.swift:253, readable_error_code=CONFIGURATION_ERROR, 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} userCancelled: False

 

 

We have a production app with several thousand users per day, but for a small percentage of them, we encounter the error described above. Unfortunately, we have not been able to identify any commonalities among users experiencing this issue. They are from various countries, using different app versions, and all are on physical devices (not simulators).

 

Currently, 1.3% of our iOS customers are affected by this issue. The possible causes listed here (e.g., configuration errors): https://rev.cat/why-are-offerings-empty do not apply in our case. For approximately 99% of our users, this error does not occur. However, the fact that this issue impacts several hundred users monthly is resulting in significant revenue loss, which is unacceptable. Unfortunately, we have no clear understanding of why this error happens or how to address it.

 

This error also occurs somewhat frequently during the Apple review process, although those instances have been excluded from this analysis.

 

To summarize:

  • There is no configuration error.
  • All subscription products have been successfully reviewed and are globally available.
  • Paid Application Agreements are signed.
  • We are not using any StoreKit Configuration file.
  • The reference names in App Store Connect have never been altered since the products were created.
  • Errors are being tracked on physical devices, not simulators.
  • These errors have been reported by real users, not just the Apple review team.

We are currently at a standstill and urgently need guidance on how to investigate and resolve this issue.

Sincere apologies for not responding earlier. We were trying to investigate the problem but haven’t verified our theories yet. We’re trying to verify whether this could be caused by users not being able to make payment so StoreKit won’t return the your in-app purchase products. https://developer.apple.com/documentation/storekit/appstore/canmakepayments 

​@Greenie Cheng Are you able to provide any update?

Hi ​@Christian Kapplmüller apologies for the delay. We are internally looking into and testing this but would like to know if this is happening for all of your apps or just a select few?

Hi  ​@Haley Pace ,

We’re seeing this issue across all of our apps, and the frequency of occurrence seems to correlate with the number of installs/users. Unfortunately, we haven’t identified any common factors that could explain it. Here are a few observations:

  • Countries: The issue occurs globally — we’ve seen it in China, the US, Mexico, Europe, and essentially everywhere.
  • Devices: It happens across many different iOS devices.
  • App Review: The issue appears both in production and during app reviews, with a noticeable increase in frequency during the review process.
  • App Versions: It affects multiple app versions, dating back at least a few months.

Based on these observations, we believe this is not a configuration error on our end. Could it be that server-to-server communication between RC and Apple is failing in some cases, and some of these errors are being incorrectly reported as “Configuration Error”?

 

Please let us know if there’s any further investigation we can do on our side or additional information you might need.

 

Reply


Terms & ConditionsCookie settings