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

Show first post
This post has been closed for comments

28 replies

S
jeffrey_bunn wrote:

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 followed all of this but still. I am stuck with this for a month now

S
stevie658jjh wrote:
jeffrey_bunn wrote:

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

G
  • god
  • New Member
  • 1 reply
  • April 6, 2025

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.

Most helpful members this week

Terms & ConditionsCookie settings

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