I’ve used Natively to wrap a Bubble app and gone through all the guides to set up in-app purchases with RevenueCat.
I’ve set up the products in both Apple Connect and Google Play stores.
I’ve linked those to RevenueCat and set up Entitlements and Offerings / Packages.
I am now trying to get this all linked up in Bubble, but not having any luck.
If there is anyone willing to spend an hour (max) with me to go through my setup to see if there’s anything I’m missing or can help me get this up and running - it will be greatly appreciated.
We have web payments working fine through Stripe, but because this app is submitted to the app stores, they require in-app payments to be set up.
Hi @drmattcrooks - we ended up getting help from the folks at Natively.
But in the end it came down to a few things - all app store setup related.
Play store needed to go through closed loop testing first, required updated screenshots.
Apple connect was missing tax forms from the client, needed links to the EULA t&c’s in app.
So all in all, was just a lot of setup stuff, not so much issues in our app.
Hopefully the will be a way to make some of this stuff easier when native mobile gets rolled out fully.
Hello @kevin_v
I’ve been fighting day and night for several weeks to set up Apple IAP in-app payment in our application but it’s blocked.
We manage to display the payment button on TestFlight (sandbox), when we click on the button the payment is accepted with the little native popup that says “payment accepted” but the payment doesn’t reach our database, so we don’t know if the customer has paid in our database, no payment information.
We downloaded the webtonative plugin and purchased the feature from webtonative.
Could you help us if I send you some screenshots?
Best regards.
Hi @elarchi75 - we used Natively and unfortunately not familiar with Webtonative.
Doubt I’d be much help to you - sorry. Is there any support available from Webtonative?
We ended getting quite a bit of support from the guys at Natively.
Hi Kevin
I’d like to ask you a quick question. How do you find a user who pays for an in-app purchase, knowing that you retrieve the purchase data via a webhook from Revenue Cat, and in the backend workflow you can’t link the data to the user who clicked for the purchase? When you make a purchase, do you send Revenue Cat an id that the user has in Bubbe (unique id), and when you retrieve the data from Revenue Cat via the webhook, you find the id that you sent to Revenue Cat (API GET or POST) and you can assign it to the user?
You have to make sure that you set the revenue cat ID yourself otherwise it will assign an id for you. Simply set the id to the user id and you can match them.
Thank you very much sem for this reply, I’ve been trying to solve this problem for several weeks now, and it’s very difficult for me, even though I know it’s not complicated at all, but I’m not comfortable with APIs. I can’t match the user’s unique id on Bubble with the RC id because after payment I receive the user’s RC id on my workflow backend (webhook) and at that point there’s no proof that it belongs to the user who paid. Basically, if everything happened on the workflow and not on the workflow backend, I’d be able to do everything without any problem, but I can’t get the payment data from my workflow. I’m exhausted, I assure you. A little help to solve this problem would do me a world of good.
You have to look for the build natively Purchases element and put that on your page. Make sure that you call this to set the ID BEFORE your customer makes a purchase or calls the RevenueCat API. As soon as you let anywhere in your app call the RevenueCat API without setting the user ID first it will assign a revenuecat ID.
Also look into RevenueCat aliasses as it will add as many ID’s to a user as you or another process adds. So you will find an array of user ID’s from the past and current one. So you can add to any user the ID (for instance on login you can always check if there is the bubble user id in there or not, if not simply call the Purchases element and add it).
When you are not familiar with API calls it will get difficult. So either you have to find some tutorials about it or ask someone to do it for you. It is not hard, but you have to know the basics. So if you want to learn give yourself a day, sit back and relax, take a cup of coffee or something and enjoy a day learning all about API’s and the Bubble API connector.
For instance, the picture you showed is a GET api (for getting things like information from RevenueCat). If you want to send something to revenuecat you need to post things so a POST request.
About not using build natively plugin…not sure how you use the SDK from RevenueCat then. So if you use build natively as a wrapper for you lr mobile app, use their plugin actions and states.
