Skip to main content

The last thing that I see in logs from RevenueCat is:
`CustomerInfo cache is stale, updating from network in foreground.`
Full log attached. 
 

SDK version: 5.21.0 (iOS)

purchases_flutter: ^8.7.3
purchases_ui_flutter: ^8.7.3

iOS version 18.4.1, not simulator. Not reproducible on all devices only on some.

No code was changed, old version of the app stopped working but worked previously.

This line `await RevenueCatUI.presentPaywallIfNeeded(value.entitlementId);` never finished. Waited 5+ minutes. No timeouts or other errors.

Hey ​@eldar-prylutskyi ,

We’re seeing an increased number of errors related to RevenueCat offerings and paywall presentation on iOS 18.4 and 18.4.1, affecting both StoreKit 1 and StoreKit 2 apps - this is a known issue reported by multiple developers, even when no code or configuration changes were made.

The timing and nature of these errors suggest a link to networking and StoreKit changes introduced in iOS 18.4, although we are still investigating whether all cases are solely due to iOS changes or if configuration differences may also contribute.

It’s important to note that most reports concern issues in the iOS 18.4 simulator environment. However, there are also cases (including yours) of similar problems occurring on some physical devices running iOS 18.4 or 18.4.1. The issue does not affect all devices and may depend on device-specific or network-specific factors.

What we recommend for now:

  • update to the latest RevenueCat SDKs: `purchases_flutter` and `purchases_ui_flutter` v8.7.4 - yours is quite recent, but just to be on the latest
  • wrap your `presentPaywallIfNeeded` call with a timeout handler to avoid indefinite hangs
  • (optional sanity check): confirm whether affected devices are using VPNs, DNS filters, or content blockers that could interfere with network requests.

To help us further isolate the issue, could you please:

  • test on devices running iOS < 18.4 (e.g., 18.3.x or 17.x) to verify if the issue persists.
  • test the same device(s) on different networks (WiFi and cellular).
  • if possible, test on other physical devices running iOS 18.4 or 18.4.1.

We are actively tracking this internally and monitoring related reports (GitHub #4954) and other community (e.g here and here) discussions.
 

Sign out from sandbox account and device reboot helped on affected device.

We tested on other devices with also 18.4.1 and 18.3 - there were no issues there.

I will ask if some VPN was used on affected device and come back.

No, VPN or any other content blockers were not present on affected device

Hey ​@eldar-prylutskyi ,

We are still tracking this issue internally, although we have been seeing it behaving intermittently in our tests. Could you confirm that this is only reproducible in a sandbox environment? Or do you see it in production too?

The above mentioned GitHub issue #4954 is being monitored too by our team, and we will make sure to have updates there as we have more insights.

Thanks for your patience here!

Hello ​@guilherme !

Thank you for writing the status of the issue!

We saw the issue only in sandbox environment as for now. I hope that it will not affect our users.

Best Regards

Eldar

Terms & ConditionsCookie settings