Unable to auto restore Amazon Subscriptions via Unity IAP

Hi All,

I have integrated the latest Unity IAP plugin (v2.2.7), and Package Manager (v2.2.2), however, we are seeing odd behaviour when attempting to auto-restore purchases from the IAP plugin (app launch), and further more, odd behaviours on attempting to Purchase same IAP again.

Issue 1) We understand the Amazon Store uses a different model when managing Subscriptions as an IAP type. Amazon uses parent-child model for these products, unlike Google and iOS stores. The way we handle this is adding both parent and child product ID as products to the configuration builder. The purchase is made to the parent subscription product, and the Purchase Success callback correctly returns its Receipt. However, on consequently app launch this parent (and child) product is restored with no valid receipt. i.e. hasReceipt is null or empty. Is this a known issue? Is there anything else we can try?

Issue 2) In the scenario above, user decides to purchase the product again. The Purchase callback returns ALREADY_PURCHASED response for the parent product, but the ReceiptID in the receipt payload is empty! i.e.

Unity Purchasing Amazon D onPurchaseResponse
I ALREADY_PURCHASED
Unity I [PurchasingService] Purchase OK
I + Type: Subscription
I + Receipt: {"Store":"AmazonApps","TransactionID":"","Payload":"{\"receiptId\":\"\",\"userId\":\"sadjkhasjkdhayyandbbXXssdsjhZak",\"isSandbox\":false}"}

Q) We can see that the latest IAP plugin SubscriptionManager class adds support for handling Amazon subscriptions, though also, seems to be giving us incorrect data. Is this available for use?

We feel that there are a number of open issues on Amazon Subscription handling with the latest IAP plugin, but before making decisions whether to use it or move to another implementation, we would like to know where the problem may lie. Any help from Unity IAP team here would be greatly appreciated

PS> We don't have this issue with Non-Consumable IAP, so I am guessing the problem lies in adapting the parent-child subscription model

Dioni

 

Hi Jeff, I meant app launch (subsequent app launch after making a subscription purchase), we expect the store controller to return products with a receipt value, however, the receipt is null.

On further inspection, on app reinstall in the same device, the subscription product is also NOT restored. Showing as no owned (null receipt). When attempting to purchase the subscription again, the Amazon Purchase returns ALREADY_OWNED response.

I don't believe there is another way to restore purchases on Amazon via the Unity IAP, right?

 

Thanks! Please let us know as soon as you can. We are attempting to adapt Unity IAP implementation for subscriptions for Amazon Store, but if issues do persist, we will have to try alternative implementations.

 

Hi @JeffDUnity3D

Faced almost the same problem.
1) Buy a subscription,
2) There is a new subscription in Amazon Appstore app in "Subscriptions" section
3) Restart application
4) There is no receipt neither for parent nor for child subscription inside corresponding product objects in

IStoreListener.OnInitialized()

callback

There is a comment near

UnityEngine.Purchasing.Product.hasReceipt

member:

// Owned Non Consumables and Subscriptions should always have receipts

But we have no.

Was this issues fixed? How can we handle it?

Unity 2019.4.18
Unity IAP 3.2.3
Fire HD 8 (10th generation) device with Fire OS 7.3.2.1
Got the bug via Live Test testing

 

Thanks for response @JeffDUnity3D !
Are there any approximate update dates?
Сan we somehow track the progress?

 

Any updates on this one? I have met the same problem with Unity IAP 4.4.0.
Have to say it started from some specific LAT launch, previous launches with 4.4.0 behaved ok.
Maybe this is Amazon side related issue, but bumping up the thread anyway just to refresh the status from Unity IAP team.

 

Any update for this issue? @JeffDUnity3D

 

Just to clarify on my previous post - after reaching Amazon support they have made some changes to fix subscription restore issue in LAT, so that has to be Amazon side related issue.