You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 23, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 23, 2025. It is now read-only.
Hi, I have a question to make, is there a way for me to manually present paywalls? Based on the documentation, I know it's supported, but I haven't found the corresponding method in RN.
Use-case
I'm trying to setup Superwall in a very mature app, with many payment flows set in place.
I tried following the documentation as closely as I could, but never got to see a paywall presented in either iOS or Android, sim/emulator or physical device.
No errors are logged on Metro, but, by running the app through Xcode, I saw the following warnings:
I was already questioning the prospect of retroactively adding all app events on Superwall and re-configuring all payments flows, but seeing as I can't even get the paywall displayed upon pressing a CTA Banner, I'm scared of going forward with the implementation and giving up the existing system (which works).
It would be much better to have a way to fallback to the existing system if Superwall fails, be it on-device or via a Feature Flag, and to that end I just want to manually present the paywalls for now.
I did, but it didn't help me pin-point the source of the issue, unfortunately.
I'm using RevenueCat, so I followed the guide to setup the subscription-related logic, and I've verified that the Superwall.shared.subscriptionStatus is properly set to inactive.
Upon futher revision, I realized the issue only happens whilst debugging. I created a Testflight build, and by having that installed I'm able to see the Paywall. I'm not using StoreKit.
My question remains, though, would it be possible to manually control the retrieval/presentation logic? It would make it much easier to adopt.
would also like to know if it is possible to manually display the paywall in React-Native. The documentation shows how to achieve this in swift, objective-c and kotlin
Activity
jakemor commentedon Jun 25, 2024
Hey! That warning is unrelated, it has to do with event tracking.
Sorry you're experiencing problems!
Have you tried this guide? https://superwall.com/docs/troubleshooting
brenodt commentedon Jun 25, 2024
I did, but it didn't help me pin-point the source of the issue, unfortunately.
I'm using RevenueCat, so I followed the guide to setup the subscription-related logic, and I've verified that the
Superwall.shared.subscriptionStatusis properly set to inactive.Upon futher revision, I realized the issue only happens whilst debugging. I created a Testflight build, and by having that installed I'm able to see the Paywall. I'm not using StoreKit.
My question remains, though, would it be possible to manually control the retrieval/presentation logic? It would make it much easier to adopt.
bjollans commentedon Jul 11, 2024
Hey, I had the same issue on an emulator and on a physical phone, using Expo.
I got it to work both times by
mostafahazim commentedon Aug 13, 2024
would also like to know if it is possible to manually display the paywall in React-Native. The documentation shows how to achieve this in swift, objective-c and kotlin