Skip to main content

Now, I may just be paranoid but ALL initiated purchases on my app in the last week ended in this “Purchase was cancelled” error, which to me, seems highly on unlikely for an app that used to get purchases every few days. 
 

I wonder whether users really cancelled all these purchases or is there something else going on here.

{
"nativeStackAndroid": n],
"userInfo": {
"userCancelled": true,
"code": 1,
"underlyingErrorMessage": "Error updating purchases. DebugMessage: . ErrorCode: 1.",
"readableErrorCode": "PurchaseCancelledError",
"readable_error_code": "PurchaseCancelledError",
"message": "Purchase was cancelled."
},
"code": "1",
"userCancelled": true
}

 

Hi ​@azerty!

I totally understand that this can feel concerning. Here is our documentation on the PURCHASE_CANCELLED_ERROR message. It typically means that the user did not proceed with the in-app purchase, which can be from either cancelling the flow or leaving the app.

Besides a high rate of these errors, have you seen any other clues that users may not be cancelling the flow themselves, or any users reaching out to you regarding being unable to purchase?


I also just noticed that some of my subscribers are subscribing as Sanbox users. How’s this even possible when they’re not my test users?


Device Info: {"os":"android","osVersion":33,"appVersion":"1.0.186","canUserMakePurchases":true}

Error: {"nativeStackAndroid":[],"userInfo":{"underlyingErrorMessage":"Error when fetching products - DebugMessage: Billing Unavailable. ErrorCode: 3.","readableErrorCode":"PurchaseNotAllowedError","readable_error_code":"PurchaseNotAllowedError","message":"The device or user is not allowed to make the purchase.","code":3},"code":"3"}

This error just isn’t going away. For months now, I haven’t had up to 2 successful subscriptions. Even when `await Purchases.canMakePayments()` returns true, I still get the above error.


Hey ​@azerty,

Here’s some additional reasons that you might see Billing Unavailable: https://developer.android.com/reference/com/android/billingclient/api/BillingClient.BillingResponseCode#BILLING_UNAVAILABLE()

However, I see you’re also getting the error when fetching products. Is your app currently available on the Play Store, and has been approved and published by Google? It is unexpected that anyone besides your opted in test users could access your sandbox user.

I might encourage you to open a support ticket from your dashboard and include all information possible, including debug logs. This will allow us to communicate faster and share more information!

 


Reply