Skip to content
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

Open
brenodt opened this issue Jun 24, 2024 · 4 comments
Open

Manually retrieving/presenting paywalls #7

brenodt opened this issue Jun 24, 2024 · 4 comments

Comments

@brenodt
Copy link

brenodt commented Jun 24, 2024

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:
image

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!

@jakemor
Copy link

jakemor commented 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
Copy link
Author

brenodt commented 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.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.

@bjollans
Copy link

Hey, I had the same issue on an emulator and on a physical phone, using Expo.

I got it to work both times by

  • uninstalling the development version of the app
  • Restarting the phone
  • Deleting the android / ios output folder in my code base
  • cleaning the build cache
  • rebuilding

@mostafahazim
Copy link

mostafahazim commented 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants