Apple rejected build 1.0 (407) under Guideline 2.1(b), stating the in-app purchase products exhibited a bug: tapping “Unlock Full Access” produced no response during App Review. I’ve since reproduced this myself in TestFlight and I’m seeing the same thing: tapping the button does absolutely nothing — no native sign-in prompt, no purchase confirmation sheet, no error message, no visible response of any kind.
I have searched the community to find others with this same issue and found some issues many years ago so I am not sure what I am doing wrong. thanks for you help. Liz
Are the added product IDs and actions are correct? When you submit for review or testing through TestFlight, are the products are live and submitted for review too?
There’s another component called IAPHUB too which you can setup easily and much information on errors. : IAPHUB | Adalo Resources
Hey Dilon before I make this huge commitment with IAP HUB I want to clarify what I have already confirmed: Product ID"S match exactly on both IOS/Android across two independently configured digital purchase components - I’ve repoduced this myself in testflight sandbox testing on both buttons in my app with zero response at all, not even the apple sign in prompt on any purchase attempt.. I dont get an error of any kind, it is non responsive. - Is building this in IAPHUB going to behave differently? I have watched (most) the video on IAPHUB and that is going to be a undertaking and I questioning if I will get the same results.
In App Store Connect, do you see any crashes available in the TestFlight tab? If all good, I would suggest you to submit a support ticket so a team member can take a deep look at your setup and provide assistance.
Regarding IAPHUB, testing could be confusing too which is trial and error in the beginning but it’s quite easy to setup and something I’ve used on client apps in the past, which worked nicely! I haven’t used the digital purchase component for a long time so it’s less experience and but have much experience on setting up IAPHUB components. But it looks like you’re halfway there with the digital purchase component, so we can check if it’s an issue with the setup or if it’s actually a bug.
Two components: Lets the reviewer (or any user) reach Full Access immediately, without first having to log 5 wines
Included in review submission: This is what I’m unsure about the rejected version’s “Items Submitted” list shows only the App Version, not Full Access as a separate item. “Add for Review” is greyed out on the IAP page (since it’s already “Waiting for Review”), so I can’t tell if it was properly linked to the reviewed build
Sandbox testing: Yes — signed out of my production Apple ID, tested with a dedicated sandbox tester account, on the latest TestFlight build
Crashes: Only one, unrelated — from an old build (0.0.16/350) back on July 8. Nothing tied to build 407 or my recent tests
Again thanks for your help. This is my first time doing this and some or most are very confusing. What I am confused about is the whole full access digital purchase “being reviewed” what seems like at a different pace then my app and when that is the case and the app requires the digital purchase to work then I feel like I am going around in circles - OR, does the review at apple attach the digital purchase that being reviewed to each new bundled that is send to be reviewed??? I seems like the digital purchase part of this whole process is somehow not connected to my latest build or even my build. Should the digital purchase “full access” be listed on the items submitted? I hope this makes sense to you because it barely makes sense to me. ha. Liz
Quick update and thank you again for pointing me toward IAPHUB and the troubleshooting questions. Since then I dug in further on the App Store Connect side and found that my Full Access In-App Purchase was never properly attached to my rejected app version’s submission (Items Submitted only showed the app version, not the IAP). I’m now working directly with Apple Developer Support on getting the two properly linked into one submission.
I’ll report back here once I hear more from Apple or get it resolved, in case it’s useful for anyone else running into this with the Digital Purchase component. Appreciate all your help getting Pour Recall across the finish line. Liz
That’s great to hear, if you create a new TestFlight build in Adalo, then you can submit it for a new review attaching the IAP for the review too. How did it go?
Good grief that was complicated. Finally this all looks correct and I am waiting on review. I don’t know how long this take to work in Test Flight - I just submitted the new build and IAP for a review and when I checked on my test flight build the IAP is still not working. Maybe some kind of propagation delay… I am staying hopeful. Thanks again Dilon. cheers!
FYI - this build did not go through - the IAP is not triggering a response. It is a dead button… would deleting the IAP button in the app, then reinstalling with a new button possibly help?
Solved In-App Purchase button unresponsive - Turns out the actual cause was whitespace hidden in the component setup.
Also, a genuine thank you to Dilon on the Adalo team, who worked this issue with me start to finish. He never gave up on it. I’m not a developer by background, and at no point did I feel talked down to or made to feel like I was asking dumb questions. he was patient and encouraging the entire way through. That kind of support makes a real difference when you’re building on a no-code platform without a technical background. Thank you, Dilon you’re outstanding at what you do. I am already working on an updated version of the app so… I will be back with more questions.
But it looks like you’re halfway there with the digital purchase component, so we can check if it’s an issue with the setup or if it’s actually a bug.
cheers!
I am already working on an updated version of the app so… I will be back with more questions. 