Skip to main content
Question

Purchases.getOfferings() throw exception in dev-client mode


Forum|alt.badge.img+3
  • New Member
  • 4 replies

Hi,

In my app I am calling  Purchases.getOfferings() .

If I build my app and submit it with eas, and then install it on the mobile device with test flight:

eas build --platform ios --auto-submit

Then the offering list is returned  as expected. 

 

But when I try to run it for debugging with --dev-client , on my mobile device

npx expo start --dev-client

Then the following exception is thrown:

failed  {"code":"23","message":"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). \nMore information: https://rev.cat/why-are-offerings-empty","domain":"RevenueCat.ErrorCode","userInfo":{"readableErrorCode":"CONFIGURATION_ERROR","readable_error_code":"CONFIGURATION_ERROR","source_file":"RevenueCat/OfferingsManager.swift:125","source_function":"handleOfferingsBackendResult(with:completion:)","NSLocalizedDescription":"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). \nMore information: https://rev.cat/why-are-offerings-empty"}

What am I doing wrong? Is there another way to debug without rebuilding , submitting and installing it each time?

3 replies

Forum|alt.badge.img+3
  • Author
  • New Member
  • 4 replies
  • October 9, 2022

After I followed this guide: https://www.revenuecat.com/blog/expo-in-app-purchase-tutorial/ and build a development build first it worked.

eas build --profile development --platform ios


Forum|alt.badge.img+3
  • Author
  • New Member
  • 4 replies
  • October 9, 2022

Now I have another issue, I can’t debug the app with chrome.

Getting the following error: 

On chrome I see the following error:

WebSocket connection failed: 


Forum|alt.badge.img+3
  • Author
  • New Member
  • 4 replies
  • November 19, 2022

The issue was related to my debugger port which was not on the right port.


Reply


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