Hey @Vivek Khatri
Have you checked out this article on empty products?
This is typically caused by some configuration issue. On Android, you should double check that your app is published on a closed track and you've added a tester. I know that’s a common cause on Android.
If you can take a closer look at the debug logs, you should see more information on whether the product IDs were fetched properly from the RevenueCat API or not.
Hi @ryan
Thanks for the quick response!
My app is in ready to send for review state in alpha testing and 1 tester is also added. Also checked the article but all looks good to me
So I think it actually needs to be in the published state before you can test fetching products and making purchases, not ready to send for review.
Hi @ryan
There is no option of changing the state of the release. I can only promote it to either open testing or to production. I am not sure if I am missing out on something or the newer version of play console doesn’t have publish status for closed testing.
Can you verify this once and let me know? Would be a great help.
Does it say your build is in-review? Or do you see the option to submit it for review?
You can’t publish it yourself, you’d need to submit it for review before it would be “published” on an internal track. The Google review process can take a while, and unfortunately they won’t let you test IAP before your first build has been reviewed.
@ryan
Thanks I figured how to publish app on the new play store. It’s in review and I will check once it is published in closed channel.
However, I am getting the same empty response in apple as well. What could be the issue there.
There’s a handful of configuration problems that can cause this on iOS in this post here: https://community.revenuecat.com/sdks%2D51/why%2Dare%2Dproducts%2Dempty%2D124
I cant debug the application and cant see the exact result of subscription
Hello, did you end up figuring out the issue?. I’m also unable to fetch any offering in Android. I’m able to fetch it from AppStore but I’m unable to do the same from PlayStore.
“Could not validate subscriptions API permissions” option is not checked mark in Revenue so I’m assuming this is the reason why I can’t still fetch anything from PlayStore.
I’ve submitted Closed Testing and it’s in review so hopefully it’s fix after that.
@codeyond I was in your situation yesterday. I had a closed track with a build uploaded by not released/reviewed. We’re not able to get the app fully reviewed yet, due to a number of required steps on the Google Play dashboard.
I realized, however, that we had skipped the internal track and went straight to the closed track. So as such, there was no build rolled out at all in our Google Play project. So I created another build (had to increment the versionCode) and submitted to the internal track (rolled out). Soon after, products were successfully flowing into the app via the revenuecat sdk.
Hey! I’m a little confused. Why would we need a closed track testing before we can fetch offerings? Because if I want to publish a release to the closed track I have to complete the app details, and to complete the app details I need to add app screenshots, etc… Which seems weird that I need to add screenshots before I can even get into the app LOL!
I’m having the same issue on Android. I followed all the steps and my google credentials were verified on Revenuecat. I imported products into Revenuecat no issues there so I thought there would be no issue getting the same in the app but I was so wrong. I lost already too much time on this.
If the import of products works without closed testing why would I need to start closed testing to get the same functionality in the app? I published the up for internal testing and closed testing is under review.
My offerings are empty and I’m not sure what else I can do?