Skip to main content
Question

iOS: Error: SKProductsRequest took too long to complete.

  • June 12, 2025
  • 1 reply
  • 16 views

Forum|alt.badge.img

Very strange, never had this issue before. It’s occurring in production as well.  Tested it on several different phones and accounts, it appears to be happening to one of my co-workers on both prod and Testflight. 

I’m using react-native-purchase v7.27.3

happens when calling Purchases.getOfferings
 

Seen there was a post from a year ago talking about it, but it doesn’t seem like there was a solution to the issue.

This post has been closed for comments

1 reply

guilherme
RevenueCat Staff
Forum|alt.badge.img+4
  • RevenueCat Staff
  • 66 replies
  • June 16, 2025

Hey ​@fred-8eea7e ,

We’ve seen a number of reports across different environments (Production, TestFlight, and Sandbox) that seem to be intermittent and seems to affect only a subset of users, sometimes only in certain environments, sometimes in production.

These tend to often be related to Apple’s StoreKit not returning product info in time, which is unfortunately outside of RevenueCat’s direct control. We’ve also seen this caused by network issues on the device, VPNs, ad blockers, firewalls, or even issues on Apple’s side. Occasionally, Apple’s sandbox/test environments can be especially flaky.

The SDK does cache product lists, but details are fetched from Apple each time, so a slow response from StoreKit can still cause this error.

What you can try:

  • If this is happening in Sandbox or TestFlight, try with a new sandbox account, delete and reinstall the app, or use a real device instead of a simulator;
  • In production, encourage affected users to check for VPNs, ad blockers, or restrictive network settings - restarting the device or reinstalling the app can sometimes help.
  • Make sure all products are approved and available in App Store Connect, and that there are no recent configuration changes that could affect product availability.
  • If possible, implement a retry/fallback mechanism in your app so users aren’t blocked by a single failed request.
  • If you’re not already, consider upgrading to the latest RevenueCat SDK, currently on 8.11.4  and enabling StoreKit 2 in your SDK config, as this has resolved some related issues for other developers.

If you have additional logs or details (device models, iOS versions, user locations, etc.), please share them, they can help us identify any patterns. 

Best,


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