I followed step on docs however, I can not get offering and error says:
There is an issue with your configuration. Check the underlying error for more details. There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect (or the StoreKit Configuration file if one is being used).
I saw there are many other developers have same issue but no solution. This was the my first time to use revenue cat but I think I will implement my own way because of this issue.
Thanks,
Page 1 / 2
Good point! I have had a similar issue a while ago, when I was setting up RevenueCat. I did not realize that you need two separate API keys for both platforms - iOS and Android.
Hi guys.
I hope that this info will help someone here:
I was using the capacitor plugin and after configuring everything - according to the docs - the products still did not show up. I accidentally discovered that I was using the RevenueCat api key, not the Apple api key. I switched the keys in the Purchases.configure method and immediately the prices from appstoreconnect became visible. Yaai.
I hope the attached screenshot will help. Good luck everyone!
For anybody reading this, it turned out that the reason my products were not being fetched was because there was an issue with my paid applications agreement. If your agreement has expired or has not been signed, the api can’t fetch any of your products.
THIS! Thank you!
issue i was having was i did not complete
content rights
age rating
once i added those, i could see the products
My Dear Friends, After struggling for many days with no hopes, finally managed to solve this issue. Most of the times it is issue with your configuration in AppStore. I guess Apple does not provide correct error messages hence revenueCat share generic error messages with us. Make sure nothing is red in your appStore subscription configuration and you have signed Paid Agreement. Paid Agreement row should have Active status.
Yes it a server issue since it is working with another provider I am using in Prod. (Glassfy)
This just started happening today with my app, after many months of it working normally. It seems to have resolved itself within a couple hours, so - sometimes i might just mean a server is temporarily down.
In my case this is not an issue with my configuration. I am testing RevenueCat as a new solution. It was working for 1 week then empty screen with this error. Using loadProducts instead of loadOfferings fix it.
What’s wrong with your solution RevenueCat?
What worked for me to fix the below error
LOG Error getting offers There is an issue with your configuration. Check the underlying error for more details. There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect (or the StoreKit Configuration file if one is being used).
I added all the products which is approved from apple (pretty sure Waiting for Review status also will work)
Then run xcode and build in simulator.
The products appeared in my paywall with getOfferings method (which was not before)
I purchased each product from simulator
I checked the Sandbox Transactions and saw the purchases.
Then I deleted the current app on real device I got a new build
I checked the debug logs on xcode and saw the product appeared after and getOfferings() worked on real device.
Hey! I’ve spent like weeks and finally solved that
I’ve set up everything as Revenue Cat said in their answers, so everything were ok
I had the same Subscription and lifetime IDs in ios and andoid → I’ve deleted products for android and created them again with a new IDs
Also be careful with “Base Plan Id” and subscription ID, Don't mix it up
Also as people said here before, it can be a problem with a cache
Hope it helps!
Just FYI, had the same issue even after fixing the paid apps agreement, and all the steps highligted in the RevenueCat thread here: https://rev.cat/why-are-offerings-empty.
What worked was just waiting for 12 hours, and saw the new products come through from Apple in the morning - no code or configuration changes on my end. Hope that helps someone!
I had this same issue. My fix was making sure all the required fields in the Business section in App Store Connected were filled out. I also made sure that I added a Bank Account. I left it for a couple hours then it worked.
Been banging my head against the wall for several days, but I got it working. Some important things to note: Accepting the paid apps agreement also includes adding the tax and bank info
After you do this, it will take several hours before the purchases become available
Things I’ve also tried that might have contributed to the success:
Import products from ASC as opposed to manually entering them
add / remove several offers in RC (mentioned above)
test app through TestFlight
I was experiencing this issue too, and have resolved it now.
I can’t be sure if it was one change, or all of them, but hopefully it helps someone out there.
Firstly, I already had a subscription in the ‘Ready for review’ state, and was still seeing issues.
My boss had signed the Apple agreements, but not yet setup a bank account, and tax info.
Once that was signed, I was still seeing the error. I left it for a couple of hours, deleted everything from Revenue Cat, and recreated products, entitlements, offerings, and a paywall.
I tried to present the paywall again, but it still didn’t work. At this point, I called the getProducts api to see what would come back, and got the product! I then called the getOfferings api and got an offering! I then tried to present the paywall one last time, and would you guess it - it works.
Others have suggested caching issues on Revenue Cats side, and I tend to agree after my experience.
I can’t be sure these steps will work, but hopefully it is of some use.
After wrestling with this issue for a few days, I finally found the reason for my case.
I did go through this guide: https://rev.cat/why-are-offerings-empty, and everything checked for me. At least, that’s what I thought. But no, I was so wrong. I had a separate bundle id for debug version. In hindsight, it’s very obvious. But as I was so deep into it, I forgot about it. So this is just a reminder to double check your bundle id for debug mode.
If you are interested in how I solved this issue, I went with the route of creating a separate app in App Store Connect for debug bundle id. From there, I set up all in-app purchases and subscriptions following the real app version. My reasoning of going this route is that it’s easier for me to test in debug mode with sandbox account and without having to switch bundle id back and forth.
And if you read this far, one more reminder to add capability In-App Purchase in Xcode’s Signing & Capabilities. I did forget about that too.
What worked for me was to create multiple offerings and populate them with all details (products, paywalls, etc). Then I removed a few. After this, the fetchOfferings worked.
It seems like some glitch on RevenueCat side, some hang-up… Creating and deleting several offerings will somehow make fetchOfferings to get data.
Every subscription was only active for Germany, and we kept getting this error when a device registered in the UK downloaded it from the app store.
If you can't solve it despite all instructions, make sure to check this situation as well.
make sure all countries are available.
Unfortunately this is not the solution for us. Does anyone from the revenuecat team actually know whats going on?
I found the solution at the end of three days.
Every subscription was only active for Germany, and we kept getting this error when a device registered in the UK downloaded it from the app store.
If you can't solve it despite all instructions, make sure to check this situation as well.
make sure all countries are available.
We had no problems in Testflight and Sandbox or Google Play, and we have never encountered such a problem before. We suddenly encountered it and our customers could not buy it. Since there is no solution to this issue in the sources, we are stopping using RevenueCat.
For anybody reading this, it turned out that the reason my products were not being fetched was because there was an issue with my paid applications agreement. If your agreement has expired or has not been signed, the api can’t fetch any of your products.
I have been dealing with the same issue for almost two weeks now. I have reset everything and retried multiple times and there is not a single thing that I can tell I did incorrectly. Therefore, I can’t see how this is related to my configuration on Appstore Connect. Has anyone here had this issue resolved?
Ended up using Adapty because I didn’t run into this issue with them. If there is an easy fix we’ll switch back to RC.
Exactly what I am doing now but, don’t expect this issue to be fixed - you have been silently affected by it for a long time.
I almost guarantee that you see an revenue increase and better statistics. 100%.
This is not an iOS config error, this is a problem with Revenuecat, don’t let them fob you off. 4 weeks waiting for a response on GitHub and now left at the last minute to swap this out for another provider.
I’ve got multiple users reporting that offerings are just not loaded - randomly.
