Skip to main content
Solved

Could not validate inappproducts and monetization API permissions

  • Jan 2, 2024 12:57 PM UTC
  • 10 replies
  • 4772 views
claus-lysholm-a1b7f0
Forum|alt.badge.img+2

Permissions to call subscriptions API is checked as validated, but not the other two.

I have gone over the configuration for the service account several times, following your documentation instructions, but never the less I’m stuck. I have also waited several days before refreshing the status again, but it’s the same. I simply don’t know what else to do know except reaching out to you.

I’m creating an app for Android with package name biz.codepower.echonotes and RevenueCat App ID app4742cd71c6.

Best answer by ali-dahud

hello @claus-lysholm-a1b7f0 ,
Did you succeed in making it work? I had the same issue but after enabling the  Google Play Android Developer API, it works now. I followed this documentation: https://www.revenuecat.com/docs/creating-play-service-credentials

I thought the google play android dev API and the Google Play Developer Reporting API were the same.

View original
    This post has been closed for comments

    10 replies

    cody
    RevenueCat Staff
    Forum|alt.badge.img+8
    • cody
    • RevenueCat Staff
    • Jan 4, 2024 4:48 PM UTC

     Hey @claus-lysholm-a1b7f0!

    Can you try making a test purchase? Sometimes the validator can get hung up if there hasn’t been a test purchase attempted.

    You can read more about testing here: https://www.revenuecat.com/docs/google-play-store

    claus-lysholm-a1b7f0
    Forum|alt.badge.img+2

    When I try to subscribe through the app, there’s no offerings available from the RevenueCat call (const offerings = await Purchases.getOfferings()). Could that not be because the RevenueCat for the Android version setup can not be completed, exactly because of the problem described in my original post?!

    Forum|alt.badge.img+2

    hello @claus-lysholm-a1b7f0 ,
    Did you succeed in making it work? I had the same issue but after enabling the  Google Play Android Developer API, it works now. I followed this documentation: https://www.revenuecat.com/docs/creating-play-service-credentials

      Forum|alt.badge.img+2
      • ali-dahud
      • Helper
      • Answer
      • Jan 25, 2024 9:06 AM UTC

      hello @claus-lysholm-a1b7f0 ,
      Did you succeed in making it work? I had the same issue but after enabling the  Google Play Android Developer API, it works now. I followed this documentation: https://www.revenuecat.com/docs/creating-play-service-credentials

      I thought the google play android dev API and the Google Play Developer Reporting API were the same.

        claus-lysholm-a1b7f0
        Forum|alt.badge.img+2

        Boom, that did it! Thought I did, but I did not have Google Play Android Developer API enabled.

        Thank you so much!

          Forum|alt.badge.img+3
          • lululucas
          • Member
          • Mar 21, 2024 6:10 AM UTC

          @ali-dahud , worked for me too. I was stuck on this all morning, thank you so much!

          Forum|alt.badge.img+2

           

          @ali-dahud 

          This was the missing link. Thanks

          Forum|alt.badge.img+2

          I’ve already added the ‘Google Play Developer Reporting API’ as provided in the link.

          However, it still says credentials need attention. It’s been way pass 36 hours for me.

          Revenuecat documentation seriously needs to be updated

           

            Forum|alt.badge.img+3
            • harsh-001
            • New Member
            • Dec 14, 2024 7:35 AM UTC
            • I have followed all steps
            • I have waited for over a week
            • I have re-did all the steps, created multiple service accounts 

            Still nothing works. Can someone please help?

             

            Forum|alt.badge.img+2

            I’m having the same issue as the previous 2 posts. I’ve made multiple accounts, I’ve followed the documentation exactly, including enabling the Google Play Android Developer API. Any insight would be greatly appreciated!

             

            Terms & ConditionsAccessibility statement