Skip to main content
Question

[React Native] Unclear behaviour and issues with Paywalls v2

E
Forum|alt.badge.img+3

Hey folks! I've just tried using Paywalls v2 instead of my own custom paywall and I find a few things confusing that I couldn't clarify in the documentation or repo. I would love to know how things are supposed to work:

  • If I press "Restore" when there is nothing to restore, I don't get either onRestoreError or onRestoreCompleted callbacks triggered. Nothing happens on the UI - the button changes to a loader for a few seconds and then just goes back to normal. I find it confusing and would expect something to happen to at least notify the user about what's happening.
  • Does the paywall close by itself after a successful purchase? I see navigation happening twice after migration from custom code, where I had a manual navigation call. But when I removed it, my testers said that in TestFlight the paywall didn't close, and moreover they couldn't close it themselves via the close button; only reloading the app helped.
  • I also noticed a new crash that appeared only on the commit adding custom paywall: App Hanging RCTBackedTextFieldDelegateAdapter.textFieldDidChange App hanging for at least 2000 ms. I'm not 100% sure if it's related to Paywalls, but would rather put it here in case it is an ongoing issue.

Would really appreciate getting an answer soon! 

2 replies

jeffrey_bunn
RevenueCat Staff
Forum|alt.badge.img+6
  • jeffrey_bunn
  • RevenueCat Staff
  • 240 replies
  • March 12, 2025

Hi ​@elvira! The restore callbacks you shared won’t fire if the underlying receipt is empty on iOS. Notably, they will fire on Android. If the user has purchases, however, the restore will go through and the callbacks will fire.

The paywall will automatically close if you use the presentPaywall or presentPaywallIfNeeded methods. If you’re using the full component (RevenueCatUI.Paywall), you’ll have to listen to the purchase callbacks and close the paywall yourself. 

Is the new crash and reports from your TestFlight users related? Having to force-close the app suggests some process is running that’s blocking the close button. Do you have any additional logs to track this down? Thanks!

E
Forum|alt.badge.img+3
  • elvira
  • Author
  • New Member
  • 1 reply
  • March 13, 2025

Hi ​@jeffrey_bunn ! Thank you for the clarifications :)

Re: crash - The new crash and reports from my TestFlight users are not related. I had the app crash in my hands right after presenting the paywall, and I saw another instance of the same crash in Sentry, confirming it wasn't a one-off issue. I decided to roll back using RevenueCat paywall for now, wanted to let you know about the crash in case someone else encounters it.

Reply


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