[React Native] Unclear behaviour and issues with Paywalls v2

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!

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.

Hi ​@elvira, thank you for the update! While you’ve already shared the App Hanging log, if you can share full debug logs that include the crash, that will help us get to the bottom of this. You can enable debug logs by following this guide. After they're enabled you'll see logs like this in the console:

[Purchases] - DEBUG: No cached entitlements, fetching
[Purchases] - DEBUG: GET /v1/subscribers/<APP_USER_ID> 200
[Purchases] - DEBUG: Purchaser info updated, sending to delegate

Please ensure the debug logs include the entire app life-cycle, including the messages printed during initialization of the SDK. The more information you include here, the better we'll be able to help. Also, please feel free to add these logs in a support ticket, if you’d prefer to keep your logs private.

Thank you!