Or maybe some way of understanding how to handle exceptions from Purchases.purchasePackage() on React Native.

Hi Cameron,

I’d suggest following the error handling section in our docs to investigate the problem. For this particular error, the most common scenarios are:

• Google server is down
• Google Play Developer API Quota exceeded
• Invalid Android package name in the RevenueCat dashboard
• Google Billing Client SERVICE_TIMEOUT error

@Miguel Carranza 

What exactly does RevenueCat’s retry mechanism look like? I shouldn’t try implementing my own retry mechanism in-app?

We’re still seeing errors and very worried about potential lost revenue:

Android 10, React Native error:

{
  "nativeStackAndroid": n],
  "userInfo": {
    "userCancelled": false,
    "code": 2,
    "underlyingErrorMessage": "Google Play Error: Invalid Value",
    "readableErrorCode": "StoreProblemError",
    "readable_error_code": "StoreProblemError",
    "message": "There was a problem with the store."
  },
  "message": "There was a problem with the store.",
  "code": "2",
  "userCancelled": false,
  "line": 53,
  "column": 1121,
  "sourceURL": "index.android.bundle"
}

Any news regarding this issue? @Miguel Carranza 
We face is quite regularly and this is very annoying for potential lost revenue as @Cameron Napoli mentioned.

Hi, I was also facing the same issue. I was using the emulator for Android app. Everything was configured successfully and was fully accurate because i have used revenuecat inapp subscriptions in many 3 to 4 apps before that one. But this error wastes my few hours.


At the end, I found you must login to Google Play store on the phone.