Detected multiple renderers concurrently rendering the same context provider

[bohdanbirdie]

Trying out the next-with-apollo resulted in warning about multiple renderers
Is this expected?
Also, is the library still maintained?

"next": "12.1.6",
 "next-with-apollo": "^5.3.0",

[nilu2039]

having the same issue, did u find any solution?

[bohdanbirdie]

@nilu2039
no, I gave up
This seems to be the problem with the package because it renders the first time to collect the nested queries, and the second time when all queries are resolved - render with the cached data

Overall, I did not find any way to use apollo client with Next (or any other SSR solution) where we could still benefit from the features of the apollo

[nilu2039]

@bohdanbirdie
I think the issue is with "getDataFromTree" from apollo because I used a different package "https://github.com/adamsoffer/next-apollo" and it had the same issue.

[imCorfitz]

This seems to be due to the version of React. If running React 17.0.2, this error does not appear in the terminal, but after upgrading to React 18, I am experiencing same as OP.

However, as it is only considered a "Warning" it shouldn't impact your application. For more information: facebook/react#22796

[moshest]

I think it's solvable if we use primary and secondary renders: facebook/react#19519

[moshest]

There are some workarounds here, but I haven't tried it yet: apollographql/apollo-client#8365