Hi @cassandra
thank you for the feedback and effort, I made some test but it looks that nothing has changed for me.
The "then do" branch of IAP purchase, in the code below, never fires.
The first log instruction inside the “click” block is executed every time the user starts the purchase flow.
For the the second one inside the then do branch nothing happens instead.
Before starting my test I created a new iOS build to be sure to include the last fixes on the platfom.
Please, let me know if I can be helpful or if I can provide further evidence.
Brian has opened this ticket back up and is taking a look at why the fix we released last week did not work. He may be reaching out for more information from you to help.
Thank you for testing!
I understand that IAP was not working as intended for android, but from your testing, this seems to also be the case for IOS. Do you know what the error is after calling the purchase block?
@dani19130a I’d like to discourage you from contacting Thunkable employees outside of official support channels. It’s wholly unnecessary. You have tagged everyone in support on this post.
Brian has replied in good faith that he is still working on the issue and asked for your assistance in doing so. He reasonably just asked if you could apply a label to your project and print out the error.
Hi @conroy33 I need to try all that I can to have a plan for this fix before changing platform and waste a year of work.
You didn’t share any useful information yet and this is very bad for us as customers.
What are you waiting for the fix? Please be transparent and say which is the plan or that this fix is not important for you, it will be more useful for us.
Hi @wei
thanks for replying, some feedback for you below, is it possible to arrange a call please and discuss it in a detailed way?
Regarding your questions
as I said, I’m experiencing the issue on Apple iPhone iOS
yes, I can see the Apple purchase popup but the problem is that the then do branch never fires, I can say this because the logging instruction with message Start Apple purchase flow is never executed
why are you talking about the freezing of the screen? Before the purchase block I placed a very simple logging instruction
Please, let me know.
Hi @martint
Thanks for your help, I did a simple test right now after setting the parameter is it consumable to false (as you suggested) but the then do branch still does not fire.
Please, dear Thunkable staff, let me know what can I do and what is your plan for fixing, I’m available for you for any kind of test or anything that can contribute to the resolution.
Hi there, i’ve been testing all day, here are my questions on your Android fix.
On the event of IAP “Purchase Subscription”, the app shows the Box twice (for box i mean the white box with green button that allows you to but the subscription from Google). So my customer is asked twice if he wants to subscribe.
Whare are the main different between “Most recent active purchases” and “Get purchase History”? I’m getting the same results and i dont know which one i should use.
My subscribtion is auto-renewing, 1 year long
What’s the definition of consumable? I mean, during the set up in the store i said my subscription would renew automatically after 1 year, does it make it consumable or not?
When trying to reach IAP docs from thunkable’s project main page by clicking on the component’s “Learn More”, it leads me to the project page again.
iap docs
These are my blocks related
After all, i want to thank you all for the great improvement and for this fix which i’m sure it’ll get better soon.
@conroy33 are there any updates on this? It’s been a month since we heard from the team on any updates to this. I have intentionally told a user it’s impossible to add these until this bug is sorted out. Can we please have an update on whether it’s fixed or not? If not, is there a timeline? If not, what does your team need from users in order to help triage this?
@jared Thanks for checking up on this. Ioannis and I have been working with specific users who are having issues to help isolate what may be going on there. IAP is a third-party library owned by someone else and we can only be test on a published app, this is a trickier situation. I can assure you and everyone else though that we are working toward a fix as quickly as possible.
