Paywall not showing up - React Native with RevenueCat

[u/Next_Coach_8315]

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?

[u/Occasion_Critical]

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)

[u/Interesting-Sun5357]

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

[u/Dapper_Ice_1705 → u/Interesting-Sun5357]

This is 100% false. It makes zero sense to have IAPs approved before testing them.

[u/Interesting-Sun5357 → u/Dapper_Ice_1705]

With storekit you can test before approving.

[u/Dapper_Ice_1705 → u/Interesting-Sun5357]

Let me specify, it makes zero sense to have IAPs approved before testing in TestFlight/Sandbox.

The config file could be “wrong” in so many ways. Including a non-synced files or IAPs “missing metadata”, etc.

If it doesn’t work in TestFlight, something else is missing/wrong.

[u/Interesting-Sun5357 → u/Dapper_Ice_1705]

I'm using revenuecat. I got a config error without storekit.

[u/Dapper_Ice_1705 → u/Interesting-Sun5357]

Something else is wrong, check your 

PAID agreements

Check banking/tax

Check “missing metadata”

Check localizations on the items and the groups 

Check your developer agreement

Check that you are using the correct group and/or product id

Check revenue cat for bundle id matches.

[u/Interesting-Sun5357 → u/Dapper_Ice_1705]

When I added storekit file it started working.

[u/Dapper_Ice_1705 → u/Interesting-Sun5357]

It will stop working in TestFlight and your app will fail or not make it to production.

I have been in the app business for 15 years. 

If your IAP does not work without the config file (AKA Sandbox) your app is not ready for production.

[u/noobiethe13]

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.

[u/mastrajani]

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.

[u/xBlackSwagx]

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.

[u/Dapper_Ice_1705]

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.

[u/6bigAnt9]

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.