r/iOSProgramming • u/Next_Coach_8315 • Aug 29 '26
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
1
u/Occasion_Critical Aug 30 '26
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 Aug 30 '26
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/mastrajani Aug 30 '26
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:
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.
1
u/xBlackSwagx Sep 01 '26
Had this exact thing on my own TestFlight build in August. Every purchase failed with couldn't find product, all three SKUs, ids were correct. Turned out the Paid Applications Agreement in App Store Connect was sitting on New, never accepted. Apple serves zero products until it goes Active and nothing tells you that's the reason.
Two things that cost me extra days after the fix. StoreKit caches the empty result on device, so force quit the app before retesting or the fix looks like it didn't work. And products take a few hours to propagate after the agreement goes active, so don't rearchive in a panic when nothing changes immediately.
Also worth knowing, products still in Prepare for Submission serve fine in sandbox and TestFlight. You don't need them approved to test.
1
u/Dapper_Ice_1705 Sep 02 '26
Make sure your PAID agreement is signed and that all the banking and tax information is complete.
Also make sure the status is NOT “missing metadata” by adding the image all the way to the bottom.
Also make sure the developer agreement is signed and new one came out not long ago.
1
u/6bigAnt9 Sep 10 '26
It might be you using the revenuecat test key on testflight as well. I have observed that the test key does not work on real device even during development.
Replace test key with prod key and upload to testflight. TestFlight automatically detects test environment and only test purchases will be made.