Hi @Rokas !
Can you check the full object of the error? Something like console.log(JSON.stringify(e))
) rather than just console.log(e)
@tina and @Rokas I am also experiencing this. This is the error message I get when printing everything which is not much more helpful than what is already posted
Error purchasing subscription (null): PlatformException(11, There was a credentials issue. Check the underlying error for more details., {code: 11, message: There was a credentials issue. Check the underlying error for more details., readableErrorCode: InvalidCredentialsError, readable_error_code: InvalidCredentialsError, underlyingErrorMessage: Invalid Play Store credentials., userCancelled: false}, null)
As Rokas mentioned, what’s more concerning about this is the purchase actually goes through and I get a receipt emailed me from the google play store. So if we catch errors in our application, we will show an error to the user “payment did not go through” but it actually did.
Hey @Tony
After purchasing the product, do you receive an email from Google a few minute later that the order was cancelled? How long has it been since you set up the Play Service Credentials?
@tina
After purchasing the product, do you receive an email from Google a few minute later that the order was cancelled?
Ah yes, we do get an email like this:
“This test purchase was cancelled because it was not acknowledged. You should ensure all purchases are acknowledged so they are not subject to refunds. For more information see”
I’m not sure what this all means though!
How long has it been since you set up the Play Service Credentials?
I set them up a few hours ago
Hey @Tony !
Sorry for the delay here. Since Play Store service credentials take up to 36+ hours to propagate throughout Google’s servers, we recommend waiting some time before attempting to purchase. You’ll receive that email from Google if your service credentials are not working yet. It has been some time since your last response, is everything looking good on the credentials side?
As title says, getting "There was a credentials issue." on android after 72+ hours.
I am using `"react-native-purchases": "^4.2.0"`. Followed this guide https://docs.revenuecat.com/docs/creating-play-service-credentials#2-create-service-account to setup service account.
Subscription purchase goes through (and buying the same 2nd time Google says it is already purchased, but when RevenueCat tries to validate recipe, it says:
```
07-23 11:59:32.855 32097 3011 D 3Purchases] - DEBUG: API request started: POST /receipts
07-23 11:59:32.857 32097 3011 D 9Purchases] - DEBUG: API request completed with status: POST /receipts 503
07-23 11:59:32.858 32097 3011 E 8Purchases] - ERROR: There was a credentials issue. Check the underlying error for more details.
```
How should I solve this?
How did you manage to solve it?
There was a credentials issue. Check the underlying error for more details.
I/flutter (30735): PlatformException(11, There was a credentials issue. Check the underlying error for more details., {code: 11, message: There was a credentials issue. Check the underlying error for more details., readableErrorCode: InvalidCredentialsError, readable_error_code: InvalidCredentialsError, underlyingErrorMessage: Invalid Play Store credentials., userCancelled: false}, null)
It’s more than 36 hours what should I do now. I have very little time Please help anyone
Same problem here, 4+ days. @Faizan Rafiq Have you been able to solve it?
Any update from revenue cat? 2 weeks later and I still have the issue
Hi everyone!
I have the same issue after 72+ hours.
I’m using Google in-app subscriptions. I can subscribe on my selected plan but for some reason the process can’t finish well. I receive Google purchase confirmation email but I get an error and the subscription don’t display on RevenueCat dashboard:
2022-01-05 08:35:35.188 9549-9609/D/4Purchases] - DEBUG: Found 0 unsynced attributes for App User ID: 727771e1-9250-4bff-b08f-a3656d929f72
2022-01-05 08:35:36.124 9549-9599/D/1Purchases] - DEBUG: API request started: POST /receipts
2022-01-05 08:35:36.124 9549-9599/D/3Purchases] - DEBUG: API request completed with status: POST /receipts 503
2022-01-05 08:35:36.126 9549-9599/ E/5Purchases] - ERROR: ‼️ There was a credentials issue. Check the underlying error for more details.
What does it mean /receipts 503?
I think 503 status code means Unavailable Service
After a couple of minutes, Google cancels the subscription due to they didn’t receive a purchase
confirmation.
Followed this guide https://docs.revenuecat.com/docs/creating-play-service-credentials#2-create-service-account to setup service account.
How should I solve this? @tina
Hi everyone!
I have the same issue after 72+ hours.
I’m using Google in-app subscriptions. I can subscribe on my selected plan but for some reason the process can’t finish well. I receive Google purchase confirmation email but I get an error and the subscription don’t display on RevenueCat dashboard:
2022-01-05 08:35:35.188 9549-9609/D/4Purchases] - DEBUG: Found 0 unsynced attributes for App User ID: 727771e1-9250-4bff-b08f-a3656d929f72
2022-01-05 08:35:36.124 9549-9599/D/1Purchases] - DEBUG: API request started: POST /receipts
2022-01-05 08:35:36.124 9549-9599/D/3Purchases] - DEBUG: API request completed with status: POST /receipts 503
2022-01-05 08:35:36.126 9549-9599/ E/5Purchases] - ERROR: ‼️ There was a credentials issue. Check the underlying error for more details.
What does it mean /receipts 503?
I think 503 status code means Unavailable Service
After a couple of minutes, Google cancels the subscription due to they didn’t receive a purchase
confirmation.
Followed this guide https://docs.revenuecat.com/docs/creating-play-service-credentials#2-create-service-account to setup service account.
How should I solve this? @tina
Hi everybody! @nseb @DaveRiseUp @Faizan Rafiq @Anton Alberdi @Tony @Rokas
I was able to fix it!
My issue was regarding with credential json.
I’ve linearized json file content and that’s worked! Removed all carry return and white spaces.
Put all data in a single line like this:
{"type": "service_account","project_id": "your_project_id","private_key_id": "your_private_key_id","private_key": "-----BEGIN PRIVATE KEY-----YOUR_PRIVATE_KEY_CONTENT-----END PRIVATE KEY-----","client_email": "your_service_account_name@your_project_name.iam.gserviceaccount.com","client_id": "your_client_id","auth_uri": "https://accounts.google.com/o/oauth2/auth","token_uri": "https://oauth2.googleapis.com/token","auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs","client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/your_service_account_name%40your_project_name.iam.gserviceaccount.com"}
In my use case I was able to buy a subscription (google email confirming it), but it was not registered in revenuecat. When I request via revenuecat do I have subscriptions it’s saying no, and android is not letting me buy a new one since i already have it.
android logcat:
05-01 00:08:26.879 17567 18100 D DPurchases] - DEBUG: ℹ️ Found 0 unsynced attributes for App User ID: 7d49e418-2516-4aa7-bd15-7bb4823a0aea
05-01 00:08:27.350 17567 18042 D 0Purchases] - DEBUG: ℹ️ API request started: POST /receipts
05-01 00:08:27.353 17567 18042 D 7Purchases] - DEBUG: ℹ️ API request completed with status: POST /receipts 503
05-01 00:08:27.353 17567 18042 E 1Purchases] - ERROR: 🤖‼️ There was a credentials issue. Check the underlying error for more details.
and this is the error in react-native:
{
"nativeStackAndroid": n],
"userInfo": {
"underlyingErrorMessage": "Invalid Play Store credentials.",
"readable_error_code": "InvalidCredentialsError",
"readableErrorCode": "InvalidCredentialsError",
"userCancelled": false,
"message": "There was a credentials issue. Check the underlying error for more details.",
"code": 11
},
"message": "There was a credentials issue. Check the underlying error for more details.",
"code": "11",
"userCancelled": false
}
Things i tried:
- as @Marcos Salto said above to remove all whitespaces.
- each country has it’s own price (it was automatically filled in
service account (and json file) was created about a week ago (https://docs.revenuecat.com/docs/creating-play-service-credentials#2-create-service-account), I’ve updated in revenuecat to remove whitespaces today. my last resort is the 36+ hours wait.
any suggestions @tina?
I have the same issue after 7+days of waiting after reconfigured Google Play credentials. Any solutions?
Hi,
for me it was because I didn’t set the topic name for the real-time developer notifications.
I think the problem is because info regarding setting the topic name for real-time developer notification part is missing from the docs for setting subscriptions for Android. see here https://www.revenuecat.com/docs/creating-play-service-credentials
After you have added the google services json to your revenue cat account, you will see the topic name show. You need to take that and follow the steps to send a test notification here https://www.revenuecat.com/docs/google-server-notifications#send-test-notification