-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manually retrieving/presenting paywalls #7
Comments
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 |
I did, but it didn't help me pin-point the source of the issue, unfortunately. 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. |
Hey, I had the same issue on an emulator and on a physical phone, using Expo. I got it to work both times by
|
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 |
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.
Thanks in advance!
The text was updated successfully, but these errors were encountered: