Service Account Credentials JSON Error

Hey @wired !

We have a useful document which goes over how to troubleshoot these issues which can be found here: https://www.revenuecat.com/docs/creating-play-service-credentials#troubleshooting-the-credential-validation

This is related to permission issues setup in the Google Play Developer account where the JSON is linked to. Once these credentials pass and the permissions are granted, we will be able to verify and the issues should disappear. 

Let me know if that helps! 

Hey i followed the complete step(also created a absoluter new google cloud account for that bitte i every time get the same error

PS: i also send a test notification from google cloud (there i have no problems). I also checked the json file. The informations in there are all correct 

Hey @wired !

Could you please create a support ticket for this so we can look more into your account and see what could be missing here or causing this issue? 

Hey community,

I've been facing this issue for the past 5-6 days, where the JSON credentials file is not getting verified. I've followed every step accurately from the documentation, but it's still not working.

Here's the link to the documentation I followed: https://www.revenuecat.com/docs/service-credentials/creating-play-service-credentials

Any help would be greatly appreciated! Thanks in advance.

Hi ​@wikram-das-f5406f, for your inappproducts and monetization permissions you will want to make sure the permissions specified in our troubleshooting guide here are enabled. As it seems you have already checked this, then Google might need time to validate both your service credentials and permissions as it usually takes 36 hours, but some developers have reported it can take Google up to a week. You can try and make a test purchase as this could jumpstart the validation and we have a workaround to get them validated faster here. You'll also want to make sure that you have uploaded your signed APK or Android App Bundle and have completed all the steps to approve the release. Sometimes regenerating the service credentials may also help.