Been getting this error after adding the service account credential JSON, I’ve made sure that I followed the documentation: https://www.revenuecat.com/docs/creating-play-service-credentials but haven’t been able to resolve this.
Could not validate subscription API permission
same here, only started yesterday but have started from afresh quite a few times and still getting same error
![Strength In Numbers Badge](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/ad9785ad-84a4-4bde-98db-d0de530785fc_thumb.png)
Likewise. I have been getting the same error when trying to setup in-app purchases on android, having gone through the proper documentation. (See screenshot below). Initially thought I needed to wait 36hours, but having waited now over 48hours, I think it might be something else.
![](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/e4c81389-cdb6-4cdf-9f3f-be246a9ed09e.png)
Can I confirm whether you are both setting this up for a new project?
![Shipped It Badge](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/00177be5-17f2-4400-bea7-87c75adea50f_thumb.png)
How did you guys solve it, i am also stuck here
![Why Not Both? Badge](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/ccbc4ad2-bff5-4fe9-b65f-83bbced7a8ac_thumb.png)
I am also stuck, its been more than 48 hours and nothing. Any luck anyone?
![Shipped It Badge](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/00177be5-17f2-4400-bea7-87c75adea50f_thumb.png)
I still can't a way to fix it, i contacted the revenue cat support and this is what they replied, when i try to enable debug it throws a warning unhandled promise rejecttion, undefined is not a function, don't know what's causing these issues to happen
***I have a couple of quick questions: How long has it been since your credentials were uploaded and can you please try to create a test purchase on your app? Sometimes this cant be unchecked until a test purchase is made and seen on RevenueCat. Also, what is the project ID for this app?
Could you send debug logs that reproduce this? You can enable debug logs by following this guide. After they're enabled you'll see logs like this in the console:
[Purchases] - DEBUG: No cached entitlements, fetching
[Purchases] - DEBUG: GET /v1/subscribers/<APP_USER_ID> 200
[Purchases] - DEBUG: Purchaser info updated, sending to delegate
Please ensure the debug logs include the entire app life-cycle, including the messages printed during initialization of the SDK. The more information you include here, the better we'll be able to help.***
![Shipped It Badge](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/00177be5-17f2-4400-bea7-87c75adea50f_thumb.png)
Please let me know if you find a way to fix it
![Strength In Numbers Badge](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/ad9785ad-84a4-4bde-98db-d0de530785fc_thumb.png)
I have the same issue, Followed exactly same set of steps as documentation for my new application and the validation error pops up when I add json key file even after 24 Hrs of wait time.
![Shipped It Badge](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/00177be5-17f2-4400-bea7-87c75adea50f_thumb.png)
lo luck yet
![Strength In Numbers Badge](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/ad9785ad-84a4-4bde-98db-d0de530785fc_thumb.png)
Hi Guys, I found a solution.
This involves publishing the new app to playstore in a closed track so revenuecat is forced to have a visibility in subscription api request.
Simply follow the instructions at the following link (just for the android section):
After publishing your new app to “closed track”, it will take some time before this is approved. I did mine last night, and luckily it was approved when I checked this morning. And everything is now working smoothly as intended.
Good luck! :)
![Shipped It Badge](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/00177be5-17f2-4400-bea7-87c75adea50f_thumb.png)
Great, thankyou for letting us know
![Strength In Numbers Badge](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/ad9785ad-84a4-4bde-98db-d0de530785fc_thumb.png)
Hi, guys, I’m stuck in this point "Could not validate Subscription API Permission", someone have any found solution ,? Thanks
![Shipped It Badge](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/00177be5-17f2-4400-bea7-87c75adea50f_thumb.png)
Hi, guys, I’m stuck in this point "Could not validate Subscription API Permission", someone have any found solution ,? Thanks
Check the answer above of
Hi All,
Could not validate Subscription API Permission means that RC does not have enough information to confirm that the credentials are valid to validate a subscription. The way to solve it would be to try a purchase in sandbox with your app
![Shipped It Badge](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/00177be5-17f2-4400-bea7-87c75adea50f_thumb.png)
Hii i posted about problems i am experiencing with subscriptions api not being validated.so u suggested me to try sandbox testing.so my questions is can i do that while my app uses android.i tried to even to get offerings with react native but i get error "[Error: There is an issue with your configuration. Check the underlying error for more details.]" so i dont weather its because of that subscription issue or what?.
thank you for your time.
Yeah, you need to try a purchase in sandbox. When trying to list offerings you get the error `[Error: There is an issue with your configuration. Check the underlying error for more details.]` ? What is the underlying error?
The keys configured in RevenueCat are not used for listing offerings. Offerings uses the products configured in RevenueCat and tries to load them from Google Play
![Shipped It Badge](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/00177be5-17f2-4400-bea7-87c75adea50f_thumb.png)
hi
To everybody experiencing the same problem the issue resolved after google play store approve the app in closed testing.
![Why Not Both? Badge](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/ccbc4ad2-bff5-4fe9-b65f-83bbced7a8ac_thumb.png)
not for me I publish the app and Could not validate subscriptions API permissions still here…
I make some reviews and all the config its fine…
and we make another similar app, same config and this one runs great…. nothing is different
![Why Not Both? Badge](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/ccbc4ad2-bff5-4fe9-b65f-83bbced7a8ac_thumb.png)
Hi Guys, I found a solution.
This involves publishing the new app to playstore in a closed track so revenuecat is forced to have a visibility in subscription api request.
Simply follow the instructions at the following link (just for the android section):
After publishing your new app to “closed track”, it will take some time before this is approved. I did mine last night, and luckily it was approved when I checked this morning. And everything is now working smoothly as intended.
Good luck! :)
After publishing your new app to “closed track”, it will take some time before this is approved. I did mine last night, and luckily it was approved when I checked this morning. And everything is now working smoothly as intended.
I double checked the link above...
Going thru my Appstore submission, why is my test link disabled?
![](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/6891371a-d1c6-48df-991e-5735a0716f14.png)
Hello, I am having the same issue “Could not validate subscriptions API permissions” and there is no log at all, just this vague message. How to fix this?
I tried
@inimaga solution did not work for me. I uploaded the app to both closed testing and to production last week. Still I am seeing the same error:
![](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/ce57fa8f-3fc2-4e25-992f-9ddcc2bea519.png)
I just ran into this as well and thanks to the suggestion in this thread I was able to fix it.
Just to confirm: my “Permissions to call subscription API” check was failing. Then I pushed released a new version to closed track and as soon as it got approved, the check on RevenueCat was working.
Note: If you haven’t published to Closed track before, it can take up to 7 days for it to be approved. Once it’s approved any subsequent closed track release should be approved pretty quick (<1 hr)
![](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/a1656cdf-db38-4573-9b1e-df857960ba22.png)
![](https://uploads-us-west-2.insided.com/revenuecat-en/attachment/481aa0df-37b3-4d2e-98e3-1acfc5cf4740.png)
I was having the same problem. Then, thanks to
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.