Hi @ab-66d276, have you been able to resolve this issue? I am facing something similar.
When I try using the REST API for fetching offering, I always get the correct response.
But `offerings = await Purchases.getOfferings();` never works.
I’m curious if you found a fix.
```
curl --request GET \
--url https://api.revenuecat.com/v1/subscribers/user_id/offerings \
--header 'X-Platform: android' \
--header 'accept: application/json' \
--header 'authorization: Bearer google_api_key'
```
Hi @innocent-779e0a couldn’t get it resolved…
Hey @ab-66d276,
If your products, offerings, or packages are empty it's most likely related to a configuration or setup issue in Apple/Google. We've put together a handy guide here that outlines the common reasons for this here:
Here's how it works under the hood:
- Products are configured in each store
- Product identifiers are added to your offering configuration in the RevenueCat dashboard
- The RevenueCat SDK fetches the configuration from the RevenueCat API
- The SDK requests the products in the configuration from the stores directly
- The stores return the valid products from that request
If the stores are unable to return valid products in step 5, it means that somewhere in that cycle there is a configuration issue, and this error is returned. For example: if there is a typo in your product identifier, the request will fail. If the bundle ID doesn't match the configuration in App Store Connect (or package name for Google Play, etc.), the request will fail. If your Google Play app isn’t published on a closed track, it will also fail.