Something is out of whack with store.finishTransaction(event.transaction) IOS (UPDATE)

[Christopher_Bishop]

I am not sure what is going on, I just updated my corona to latest build and all of a sudden my in app stuff is no longer working… store.finishTransaction( event.transaction ) calls just fine but it never finishes the transaction so the next time you go to do anything you get the already purchased but not downloaded (and it is a consumable)…

Something is out of whack for sure. I haven’t even messed with this code and the app is currently working just fine in the app store all i did was update corona haven’t changed 1 line of code.

Before someoen points me to another forum link or asks me to post code, let me say this…

It is extremly simple call store.init, in call back simple store.finishTransaction(event.transaction) and store.purchase({“morecoins”}) and yes that is it
And like I said this code has been working fine and “is working fine in iTunes” all i did was udpate corona, change some graphics and recompile and now in app no longer works.

I have seen a few posts regarding finishTransaction but they all have to do with Google and since I am not using Google figured it wouldn’t be a problem but there is for sure a problem here.

Also to be clear if I roll back the code base to a previous version (not sure what public version it was->was on my hdd since Oct) everything works fine.

I would really not like having to go back 1 build at a time to see where it is broke so if someone from Corona can just look and see where “any” work was done on transactions (ios, google or otherwise) I will start at the one before.

Kind of time sensitive as I have to get my update out this week.

**********UPDATE*************
Apparently 2013.1025 is the issue, rolledback to 2013.1024 and everything is working again…
[import]uid: 174725 topic_id: 35795 reply_id: 335795[/import]

[rob]

I’ll alert the engineers. Sounds like a regression bug. [import]uid: 199310 topic_id: 35795 reply_id: 142396[/import]

[Naomi]

Wow, @cbishop0, thank you for the update. It’s good to know that IAP works fine with 1024.

Edit: I just went ahead and grabbed daily build 1026, and I tested the IAP with my project, and it worked without a problem. @cbishop0, do you mind checking if 1026 fixes the issue for you too? (And yes, I was able to purchase consumable item.)

Naomi [import]uid: 67217 topic_id: 35795 reply_id: 142403[/import]

[Christopher_Bishop]

On 1026 here is what I found…

It treats all “new” consumables like “non-consumables” but existing consumables seem to work ok, pre-1026 the new consumable items do in fact work, but swap corona out to 1026 and it will let you purchase it the one time and then the next time you go to get it you just get the dreaded “hasn’t been downloaded” message.

However, popping over to a different application “that doesn’t have an update pending approval” it works fine… kind of weird…

*****Ding, Ding, Ding, Ding******
Ok, I can confirm that whatever the issue is, it does work on 1026 and 1024 just not 1025…

And on a side note for all the IAP people that might be having issues (with IOS) (and have an update pending -> Not submitted just pending) here is the dealo…

If you attach your “new consumables” to your update and not your “orginal via manage in app” it will give you all sorts of hell… delete them and just resubmit them (and when it says they will be rejected if they are not compatiable with your existing application just say OK) they will then become avalable as inapp consumable items.
[import]uid: 174725 topic_id: 35795 reply_id: 142407[/import]

[Naomi]

@cbishop0, thank you for detailed update and info about how to handle a case like that. Good to know.

Naomi [import]uid: 67217 topic_id: 35795 reply_id: 142408[/import]

[rob]

I’ll alert the engineers. Sounds like a regression bug. [import]uid: 199310 topic_id: 35795 reply_id: 142396[/import]

[Naomi]

Wow, @cbishop0, thank you for the update. It’s good to know that IAP works fine with 1024.

Edit: I just went ahead and grabbed daily build 1026, and I tested the IAP with my project, and it worked without a problem. @cbishop0, do you mind checking if 1026 fixes the issue for you too? (And yes, I was able to purchase consumable item.)

Naomi [import]uid: 67217 topic_id: 35795 reply_id: 142403[/import]

[Christopher_Bishop]

On 1026 here is what I found…

It treats all “new” consumables like “non-consumables” but existing consumables seem to work ok, pre-1026 the new consumable items do in fact work, but swap corona out to 1026 and it will let you purchase it the one time and then the next time you go to get it you just get the dreaded “hasn’t been downloaded” message.

However, popping over to a different application “that doesn’t have an update pending approval” it works fine… kind of weird…

*****Ding, Ding, Ding, Ding******
Ok, I can confirm that whatever the issue is, it does work on 1026 and 1024 just not 1025…

And on a side note for all the IAP people that might be having issues (with IOS) (and have an update pending -> Not submitted just pending) here is the dealo…

If you attach your “new consumables” to your update and not your “orginal via manage in app” it will give you all sorts of hell… delete them and just resubmit them (and when it says they will be rejected if they are not compatiable with your existing application just say OK) they will then become avalable as inapp consumable items.
[import]uid: 174725 topic_id: 35795 reply_id: 142407[/import]

[Naomi]

@cbishop0, thank you for detailed update and info about how to handle a case like that. Good to know.

Naomi [import]uid: 67217 topic_id: 35795 reply_id: 142408[/import]