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
Anyway, I don't think user side's finish() callback should be called in that case, or maybe with a error code as a parameter. The behavior is especially weird when storekit.purchase() is called again by the user on a product with non-finished transaction in progress: this results in a failed transaction and user code's finish() callback called directly... Could be mind-bugging ;)
Any thoughts?
The text was updated successfully, but these errors were encountered:
@maxmoore14 : do you remember if it necessary to call StoreKit's finish on a failed transaction?
https://github.com/j3k0/PhoneGap-InAppPurchase-iOS/blob/master/src/ios/InAppPurchase.m#L403-L407
Anyway, I don't think user side's
finish()
callback should be called in that case, or maybe with a error code as a parameter. The behavior is especially weird whenstorekit.purchase()
is called again by the user on a product with non-finished transaction in progress: this results in a failed transaction and user code'sfinish()
callback called directly... Could be mind-bugging ;)Any thoughts?
The text was updated successfully, but these errors were encountered: