Skip to main content
Solved

Incompatible product. Product is incompatible with RevenueCat Android SDK version 6 or above and equivalent cross-platform SDKs Learn more.

  • February 2, 2023
  • 2 replies
  • 147 views

Forum|alt.badge.img+1

I’m trying to follow the basic Android consumable in-app purchase flow, and after setting a basic product in Google Play, RevenueCat is giving me this weird error:

 

Identifier: <redacted>

Platform: Play Store

Store Status: Incompatible product.

 

Product is incompatible with RevenueCat Android SDK version 6 or above and equivalent cross-platform SDKs

Learn more.

 

The documentation points to https://community.revenuecat.com/tips-discussion-56/google-i-o-22-announcements-rc-product-priorities-1620/index2.html which doesn’t seem to have anything to do with consumable / non-subscription products, so isn’t helpful. 

So far I’ve tried searching these forums and google looking for an answer or guide, and just saw another post with a similar error for flutter. Any pointers?

Best answer by Kelton

The documentation for adding credentials was a bit different than the current Google interface - 

The problem I had was that the service credentials were not correctly configured for my project. I did need to add the `Pub/Sub Admin`, as well as `Monitoring Viewer`, but I had to do them by editing the “principal’ account.

 

https://console.cloud.google.com/iam-admin/iam?project= <your-project>

 

Then instead of adding service account access to projects (shown on https://www.revenuecat.com/docs/creating-play-service-credentials, which I could not find any interface for), I added the permissions to the principal.

 

Permissions for project "Google Play Console Developer"

These permissions affect this project and all of its resources. Learn more

 

Include Google-provided role grants

VIEW BY PRINCIPALS

 

After adding the permission, I deleted the previous product and added it back in. Now it’s showing as working in revenuecat.

 

View original
Did this post help you find an answer to your question?
This post has been closed for comments

Forum|alt.badge.img+1
  • Helper
  • February 3, 2023

Edit:

This does match the warning here - https://www.revenuecat.com/docs/google-subscriptions-and-backwards-compatibility

“This could be due to invalid Play Store service credentials, a product identifier being mistyped in RevenueCat, or the product having been deleted in Google Play Console in the meantime. In these cases, a warning will be displayed in the products page and when attempting to attach such a product to an Offering.”

So I’m walking through these steps: 

To fix this problem, you can try one of the following:

  • Delete the product in RevenueCat side and re-create or import it.
  • Update your Play Store service credentials in the app's settings in RevenueCat. This will re-trigger the migration. Please allow a few minutes for the migration to complete, and then check the product status again.
  • Create a new product with a new identifier.

Forum|alt.badge.img+1
  • Helper
  • February 3, 2023

The documentation for adding credentials was a bit different than the current Google interface - 

The problem I had was that the service credentials were not correctly configured for my project. I did need to add the `Pub/Sub Admin`, as well as `Monitoring Viewer`, but I had to do them by editing the “principal’ account.

 

https://console.cloud.google.com/iam-admin/iam?project= <your-project>

 

Then instead of adding service account access to projects (shown on https://www.revenuecat.com/docs/creating-play-service-credentials, which I could not find any interface for), I added the permissions to the principal.

 

Permissions for project "Google Play Console Developer"

These permissions affect this project and all of its resources. Learn more

 

Include Google-provided role grants

VIEW BY PRINCIPALS

 

After adding the permission, I deleted the previous product and added it back in. Now it’s showing as working in revenuecat.

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings