This message was deleted.

Just wondering how you're going about refreshing your features. The instance should be updated each time you call

loadFeatures()

. The proposed fix would not work for cases when multiple SDKs are implemented in the same environment. Not all

instances

are keyed to the same api host and key.

So on every app launch I'm initialising hoist and loading features. So the instance would update once in an app session. What would be the usecase for implementing multiple SDks?

I'm still not sure what the problem might be here. Wondering if it could be React Native specific that might affect SDK lifecycle or cached feature responses. You might try using

configureCache()

and setting a

maxAge

equal to (or less than!) your

staleTTL

. Multiple SDKs per app instance - there are a few use cases: • You might have 2 different SDK keys associated with different projects that need to be loaded at the same time • You might be running the SDK on a NodeJS server which needs to keep many independent user states per each incoming request/response