That’s what we like to see! Glad you were able to get it sorted out!
Would you share what finally fixed it for you? In hopes to help the community if they face the same roadblock?
2 Likes
I’m not exactly sure if it’s the reviewer or their environment changed, but this was the last change I did
Making the iAP Non-Renewing and resubmitting it with a new binary.
1 Like
great to hear, sorry for the late response 
2 Likes
Hey tbel, thats very interesting. Usually non-renewing subscriptions require a restore button (which adalo doesnt support).
As you have said above, it really depends on the reviewer. I had a situation where I loaded my app onto the appstore on different apps with non-renewing and sometimes it is accepted and sometimes not accepted as some reviewers request specifically the “Restore Button” which Adalo doesn’t currently support. I found that consumable usually work without issue.
In any case congrats on your app.
Thx! And yeah could be the reviewer. However during my testing when using non-renewing, I was actually given the option to restore my previous purchase, so this might’ve changed?
Thx for the reply!
Oh, restore is now implemented? How did you access it? I checked and theree no “toggle” or different button to restore?
Are we supposed to use the same iAp button but rename to restore and then for non recurring it recognises the purchase Apple side?
The modal came up when I repurchased in TestFlight, it wasn’t implemented by me, so I’m not 100% which end is in control. This however may only be in TestFlight, I have no way in testing in production without purchase for realz 
Very good question! @yelkhayami
I have just re built another testflight, and I am testing this with a non-renewing subscription. It does yes recognise that you have purchased the subscription in the past. But obviously it doesn’t recognise if it is expired as the Plan End Dates are not handeld within the iAp, only on the Adalo database. So It will be interesting to see if this satisifes the Apple Review Process. My main fear for this workflow is that the user must click “Subscribe” then Sign in, before they will know if they have or havn’t purchased the subscription in the past, some may feel this is a step to close to “repurchasing” it again as opposed to a simple check if they have or haven’t purchased in the past. I am going to resubmit to apple and see if this satisfies their review process. Previously I tailored the purchases to consumable, calling it “credits” or something similar.
For me this documentation references a toggle or a mode that we cannot access or change/toggle?
@Experts @ben1 @adalojosh can any of you guys clarify this? As far as I can see, I do not think the Digitial iAp is set up to restore non-renewing purchases correctly as per Apples Guidelines, from experience, it’s completely hit or miss whether Apple will approve the non-renewing subscription or not. I’ve had it accepted once, but refused three times on 2 different apps, applied very similarly. All relating back to restoring purchases.
Can anyone clarify this “restore mode” or “toggle” thats being referenced?
1 Like
Yup definitely let me know your outcome. Very curious.
@iAppsNi I forgot to mention that both types got approved, although I’m only pointing to non-renewing atm
@tbel So I resubmitted again with the non-renewing iAp after it failed several times. This time it was accepted, and I think I can give some indication as to why it passed this time and not before. Some requirements I gathered from the process to improve your chances of approval. I know you already got yours approved @tbel so the below is to shed some light on improving the likelyhood of passing for others reading this post.
- You can use both iAp Consumable and Non-Renewing. But be careful using consumable for subscription type purchases.
- The iAp Consumable cannot be used to deceive the customer or mislead the customer to make it feel like a subscription when it is not.
- Apple need to see a list of “Subscriptions” that your app offers, and a list of Subscriptions the logged in user has purchased. So you are best clearly having two lists for the logged in Users, such as “My Subscriptions” (Filter these by the subscriptions the user has bought) & “All Subscriptions” (Filter these by the subscriptions the user has not bought)
- For the “All Subscriptions List” set up your iAp Purchase button, and update > logged in user > add current subscription. Name the button something like Subscribe, Purchase or Buy. Clearly define what is being bought, duration, and what it unlocks. Be sure to update the iAp metadata with a screenshot for their review and for the store promo iAp image.
- For “My Subscriptionsc List” i.e. the ones the user has purchased successfully there’s a couple of things that were important for Apple review process:
5.1. Clearly define when the subscription is due to end.
5.1 Clearly rename the Adalo iAp button with “Restore/Renew” NOT buy or purchase. As this product should be in the users previously purchased list, we know that it will also be recognised for the Apple Users account based in the iAp ID that they purchased in the past.
To be double sure, I added the same purchased list into the users settings page, and a clearly defined “Plan End Date”.
A tutorial on this would be highly beneficial.
But in short, non-renewing subscriptions are possible. If you stick with something similar to the above.
If you are wondering how to set up a subscription type model in your app without waiting on the Auto Renewing Subscription iAp component this is a proven solution below that I set up in mine.
- Set up an action when a user arrives to the home screen which will redirect (sometimes) if the current users plan end date is before current date.
- If the user end date has passed they will be redirected to the paywall where I have set up to allow the user to purchase +60 days from today. +90 days +180 days etc…
- When the iAp google/Apple payment is successful, I update the current user end date by +60, +90, +180 days from current time (today).
This checking process will then make the user hit a paywall to then manually purchase more days/credits.
To add a trial of 14-30 days, when a user signs up I set user end date by +14 or +30 from today.
Hope this helps, someone, as it’s very easy to give up ! Consumables are easy to get passed usually for non subscription type purchases, like unlocking a feature, or work out, or training plan.
4 Likes
This is precisely what I did, the text states how long it’s for and when they user “purchases” I print out their end date (in my case 30days) on purchase and in their profile page.
Great write-up!
Cheers
1 Like
Hello
thank you for explaining in details there is somewhere I dont understand. Is there a link to a you-tube video that explains what you are saying?
thank you
It would make a very good tutorial, but sorry none atm
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.