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

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.

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

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...

Same issue, since iOS 18.0

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

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. 

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

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. 

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.

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

Same issue. My app has been rejected because of this

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

I followed all of this but still. I am stuck with this for a month now

Hey! I was able to fix this issue. I'm going to write the exact steps I made. Not sure what combination helped:

- At the time of writing, there is a place in appstore connect called "Business" there is an agreement and it includes tax stuff. Fill those in.

- I also added a valid bank account, and that is in "Active" status. Also found in the Business page.

- I edited the in-app purchase review screenshot I have. With the idea that there would be a change in the product so that might trigger some kind of change in the system.

- I pressed "add to review" in apple, but it gave me an error: you need to add 13" tablet images. I hoped this would trigger a change.

- I created a new product and offering along with a new paywall on the revenuecat side and attached everything together. I set that new offering as default. I added the product with revenuecat's own "get products" button.

- It did not work right after changes. I waited 3h and it worked without additional changes. It was around 24h after the tax things were set and 5h after bank account was added.

Note: I was able to test everything without a sandbox account or anything special on a testflight build on a real device. iOS told me that it's a testing purchase and will not be charged. I just used my own apple id. (None of this I found in revenuecat docs.) I have not tested anything on simulator.

Here’s what worked for me for iOS:

Since my app wasn’t published/live yet on the app store, I had to create a storekit file → sync products → connect it to a staging scheme where the scheme uses the Storekit file.

This resolved it for me, at least temporarily, while I develop the app and until we publish.

Run the development version of your app in the new scheme you created (duplicate the original) then trigger the paywall within it and it should work.

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. 

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

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  

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.

@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)

Any idea about how to resolve this issue ?

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