⚠️ IAPHUB Paywall AFTER the registration (not before)

[DGR]

Hi community, this is some sort of Hail Mary as i have not been able to find any tutorial or specific support on this in Youtube or even IAPHUB/Adalo documentation ( I already reviewed all Adalo+Iaphub tutorials in YT and the respective official documentation).

Context: Im an engineer (EE, not Software) 44yo (probably a bit old for most folks here hehe) ive been 20 years doing tech sales (intel). Ive “lightly” programmed in assembler, verilog, C++ before but i have understanding of concepts, structures, Apis, DBs, data etc. Not a Sw engineer or Dev at all, but I understand something about everything.

I made a MOBILE app with Adalo+IAPHUB and submitted to appstore and playstore.
The appflow is something like:

Onboarding screens > Registration (name, pass, email) > IAPHUB Paywall > App

I set up IAPHUB component as paywall and I got it runnning and communicating with the stores with no problem. I will be selling 1 month and 1 year subscription and their transactions were showing in the sandbox with no issues.

After submitting my app got rejected from the appstore and requested to move the paywall BEFORE the registration part to look something like:

Onboarding screens > IAPHUB Paywall > Regstration > App

This is causing a lot of problems with IAPHUB and the app is not working anymore.

From my own wanderings i think that the issue comes from (its a theory based on how I see the db registers behave in Adalo and IAPHUB):

Before, I registered the user in Adalo and then stored IAPHUB generated user ID after the user paid.
Now, the user is paying before creating a registered user in Adalo (so I have no User register in Adalos DB) and I havent found a way to retrieve user ID from IAPHUB, add it to Adalos database BEFORE the user registration extist, and then linking it to Adalos user that will be created after.

Has anyone faced a similar problem? Do you have any theory or pointers on where should I look for a solution?

Thanks in advance for your help!

[diegozane]

I had a bit of back and forth with Apple about this.

My app flow was “User registers - upload verification document - paywall”

In their very vague way of refusing the build, I finally figured out that the document upload stage was their cause for concern, as they believed I would then contact the user and get them to subscribe externally without using in-app purchase.

I moved the document upload section to follow after the paywall and they seemed fine with it.

I was very specific in the notes section for testing on App Store Connect that the paywall will only work with a registered user. After that they approved the app.

I think you’ve just got to stand your ground and be very specific about your app requirements.

Best of luck