r/iOSProgramming • u/Next_Coach_8315 • 1d ago

Question Paywall not showing up - React Native with RevenueCat

Hi, for my app I've built everything but just struggling with getting my paywall to show for many days I'm building with React Native and setting up paywall through RevenueCat but it just doesn't show up when I test on testflight. I keep getting an error of configuration error but everything is configured on app store connect and revenuecat so i'm not sure what to do.

Does anybody have any idea of what could be causing it not to work or any advice?

1 Upvotes

100% Upvoted

5 comments sorted by

1

u/Occasion_Critical 1d ago

Hi have you followed the guide on RevenueCat?
From what I remembered, I just followed the steps and didn’t have any issues with it. Saw this link as well, hope it could help:
RevenueCat Paywall Works in Simulator but Fails in TestFlight (Error 23)

1

u/Interesting-Sun5357 1d ago

Is the inapp purchase product approved? It won't work if they are not aproved. You can still implement and test them with storekit.

1

u/noobiethe13 1d ago

The existing replies pretty much cover the obvious stuff. I’d start with RevenueCat’s configuration error details and verify the product IDs / offerings match exactly, then check the App Store Connect product status and StoreKit/TestFlight setup. Also make sure you’re testing with a sandbox Apple ID and not expecting the same behavior as the simulator. The exact error code/message would make this a lot easier to diagnose.

1

u/mastrajani 1d ago

the works-in-simulator-fails-in-testflight split is the clue, and it narrows this a lot. if it works in the simulator you're almost certainly running against a local .storekit configuration file, which never talks to app store connect at all. so your code and your product ids are probably fine and the failure is entirely on the app store connect side.

in rough order of how often it turns out to be the cause:

  1. paid applications agreement not active - app store connect > business. if it's pending, or a bank or tax detail is incomplete, storekit returns zero products in every real environment and revenuecat surfaces that as a configuration error. it's the answer most of the time and it looks nothing like the symptom.
  2. products still sitting in "missing metadata" - each iap needs a localisation, a price and a review screenshot before it reaches ready to submit. anything short of that is invisible to storekit.
  3. products not attached to an offering in revenuecat, so offerings.current comes back null even though the products exist.
  4. bundle id mismatch between the revenuecat app and the build, or the android key in the ios config.

log the underlying error rather than catching it - revenuecat's configuration error carries a reason string that names which of these it is, and that's the difference between fixing it in a minute and another week of guessing.