Re-Subscribe from AppStore does not get a response from UnityIAP for specific accounts.

Hi,

I’ve got several reports from customers recently that they cannot re-subscribe a subscription product from AppStore.

The common circumstance they have is they subscribed to the subscription product years ago and they want to subscribe again. They said that they pressed the subscribe button and observed nothing happened.

I cannot find any related exception reports for it so I assume that there are not script exceptions.
It’s hard to say I reproduced the scenario but here is a similar one that I have.

I tried to reproduce it with sandbox accounts which subscribed many times before, and I observed that some of the accounts do not get “ProcessPurchase” call-back with followed console log .

UnityIAP: PurchaseProduct: com.subscription.product.id
purchase({0}): com.subscription.product.id
UnityIAP: UpdatedTransactions

Dev environment.
Unity: 2018.2.20f1
UnityIAP: 1.20
Xcode: 11.3.1

Any helps needed, thank you.

We have not heard of similar reports. You might try with IAP 1.23.4. Is your product name actually com.subscription.product.id ? I would recommend putting numerous Debug.Log statements in your callbacks and provide the full logs from you testing How To - Capturing Device Logs on iOS

Hi,

Thank you for answering.
I would not prefer to update sdk, unless I have assurance.
Please find the attached full debug log.
You can find the product id in the log file.

Thank you.

You have errors in your logs that you would want to troubleshoot. “There is a failed transaction with this product already” and “Unavailable product com.nway.powerrangerslegacywars.subscription.vip.1999mo” .Do you have steps to reproduce this error? Hopefully you haven’t deleted any IAP products on the Apple dashboard that you previously sold to your users. Are you able to purchase com.nway.powerrangerslegacywars.1999.subscription.199mo in your testing? If you continue to have issues, please add appropriate Debug.Log statements to your code, they will show in the logs. Then correlate the logs to your code for troubleshooting and provide your analysis, the logs, and the code.