RevenueCat getCustomerInfo taking ~6 seconds on fresh install, but less than or equal 1 second shortly after — why?

Hey ​@mehedi-hasan-4d1ac0 ,

RevenueCat documents that CustomerInfo is automatically fetched and cached when the SDK is configured and throughout the app lifecycle. Their docs also mention that getCustomerInfo() is safe to call frequently because, in most cases, it can return from cache without needing a network request.

So the faster second call is consistent with the expected caching behavior.

On a fresh install there may simply be no cached CustomerInfo yet, so the SDK may need to fetch the latest status before returning.

For routing, the safest approach is to configure RevenueCat as early as possible and show a short loading state while the first entitlement check completes, rather than immediately routing the user as non-premium while the request is still pending.

​@Crudyg123  is spot on! 

That slow first call followed by a fast one is the caching behavior working as intended. On a fresh install there's no cached CustomerInfo yet, so the SDK has to fetch it from the network before returning, and calls after that can usually serve straight from cache:

The latest CustomerInfo is automatically fetched and cached when the Purchases SDK is configured and throughout the lifecycle of your app, so in most cases the getCustomerInfo() method will return synchronously.

more context here: https://www.revenuecat.com/docs/test-and-launch/debugging/caching

To add one more tool in case it's helpful, if you ever need to guarantee you're reading the freshest data (say after granting something from the dashboard or your backend), you can force a refresh:

Purchases.shared.invalidateCustomerInfoCache()

Purchases.shared.getCustomerInfo { customerInfo, error in

// route based on customerInfo?.entitlements

}

Note that invalidateCustomerInfoCache() only clears the cache, it doesn't fetch on its own, so you have to call getCustomerInfo() right after to actually pull the fresh data.

One thing to keep in mind is that this won't speed up that initial fresh-install call, it forces a network round-trip by design, so it fits "I need the newest data right now" moments better than the cold-start routing decision.

For keeping the cache fresh in general without polling, enabling platform server notifications plus the CustomerInfo listener is the way to go: https://www.revenuecat.com/docs/platform-resources/server-notifications

I hope this helps, but let me know if you have any further questions!