Hydratation bug with first render

Hello,

I have followed the instructions in the readme but my page when it loads does the same query as the ssr page. However there is the NEXT_DATA with the right data. My cache is not hydrated, is it possible to have the source code of the demo so that I understand what I did wrong?

also:

In a page contained by WithApollo

export default WithApollo( { ssr : true } )( Home );

I have as props:

(2) [{…}, {…}]
0: {apolloState: {…}, apolloClient: null}
1: {}

The apolloState has the right data, how can I pass them to Apollo client ?

Thanks! 😃.

[adamsoffer]

Here’s the demo source code https://github.com/adamsoffer/next-apollo-example/tree/f4ea2ffd05e18af15589051ffcbd688d6b8019a1

(visible by visiting https://next-with-apollo.vercel.app/_src)

[aboveyunhai]

@adrienpsl just want to further enhance your implementation in case if you hadn’t meet the problem. if (globalApolloClient && initialState && !hasSetInitialStore) will be executed when initalState = {} because if ({}) is evaluated true but we don’t want to restore the empty state obviously. So the true implementation is to do a true check on empty object such as

if (globalApolloClient && !isObjectEmpty(initialState) && !hasSetInitialStore)

export function isObjectEmpty(obj: Object) {
    for(var i in obj) return false;
    return true;
}

It seems like the problem only occurs on the really first render and and then you switch pages from SSR -> SSR -> go back to previous page SSR. The empty state kicks in and cause the unwanted store. SSR to CSR back and forth wouldn’t create that empty state; And it only appears on the first time.