You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Platforms you faced the error (IOS or Android or both?)
Android
Expected behavior
isAcknowledgedAndroid should be set for both SKU types to allow for cleanly checking whether a purchase should be acknowledged.
Actual behavior
isAcknowledgedAndroid is only set for SKU types "IAP", not for subscriptions. However, subscriptions need to be acknowledged, too (see Billing library documentation). Currently, you have to check the purchase's transactionReceipt to see if the purchase has been acknowledged, or always acknowledge the purchase.
if (type.equals(BillingClient.SkuType.INAPP)) {
item.putBoolean("isAcknowledgedAndroid", purchase.isAcknowledged());
} else if (type.equals(BillingClient.SkuType.SUBS)) {
item.putBoolean("autoRenewingAndroid", purchase.isAutoRenewing());
}
Tested environment (Emulator? Real Device?)
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered:
zs-doron
changed the title
Anndroid: isAcknowledgedAndroid should be available for subscriptions
Android: isAcknowledgedAndroid should be available for subscriptions
Oct 1, 2019
Version of react-native-iap
3.4.12
Version of react-native
0.60
Platforms you faced the error (IOS or Android or both?)
Android
Expected behavior
isAcknowledgedAndroid should be set for both SKU types to allow for cleanly checking whether a purchase should be acknowledged.
Actual behavior
isAcknowledgedAndroid is only set for SKU types "IAP", not for subscriptions. However, subscriptions need to be acknowledged, too (see Billing library documentation). Currently, you have to check the purchase's transactionReceipt to see if the purchase has been acknowledged, or always acknowledge the purchase.
Tested environment (Emulator? Real Device?)
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: