Question regarding schema versioning and usage in react-native-navigation (HOC) about apollo-cache-persist

[jamesreggio]

Hi @reinvanimschoot — sorry for the slow response.

Your intuition is in line with how most React Native developers tend to initialize Apollo. Specifically, I tend to see people await the result of the init function inside componentWillMount, and then setState with the Apollo client, which gets passed into the ApolloProvider within the render function.

What I haven't seen before is a HOC like withProvider where you provide the Apollo Client in more than one place in your app. There's really no harm putting a single ApolloProvider at the very root of your app, since descendent components won't interact with it until you use a graphql HOC or query component. This is analogous to having a single Redux Provider at the root of your app, and then having individual connect HOCs where you need to access Redux state.

So, in summary, I'd suggest you use the componentWillMount approach in your app's root component, and drop the withProvider HOC. If that's not possible, you may have to store a global variable containing the Promise returned by your async init function, and then just await it from every withProvider instance.

I'm going to close the issue now, but I'm happy to continue the conversation — just let me know if anything wasn't clear.