Detected multiple renderers concurrently rendering the same context provider
See original GitHub issueTrying out the next-with-apollo
resulted in warning about multiple renderers
Is this expected?
Also, is the library still maintained?
![image](https://user-images.githubusercontent.com/23266928/172573359-d406d402-4a2a-4407-963a-0f5a800aa2af.png)
"next": "12.1.6",
"next-with-apollo": "^5.3.0",
Issue Analytics
- State:
- Created a year ago
- Reactions:4
- Comments:6
Top Results From Across the Web
WARNING - Detected multiple renderers concurrently ... - GitHub
Warning: Detected multiple renderers concurrently rendering the same context provider. This is currently unsupported.
Read more >Richard Lindsey on Twitter: "@dan_abramov -- "Detected ...
-- "Detected multiple renderers concurrently rendering the same context provider. This is currently unsupported." Is this a side-effect of having nested ...
Read more >Warning after update - Material Design for Bootstrap
index.js:2178 Warning: Detected multiple renderers concurrently rendering the same context provider. This is currently unsupported.
Read more >React native Paper Provider and React Navigation ...
Warning: Detected multiple renderers concurrently rendering the same context provider. This is currently unsupported. at AppContainer ...
Read more >react-pixi-fiber/Lobby - Gitter
Uh oh, I think I reached the limits of React: react-dom.development.js:506 Warning: Detected multiple renderers concurrently rendering the same context provider ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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: https://github.com/facebook/react/issues/22796
There are some workarounds here, but I haven’t tried it yet: https://github.com/apollographql/apollo-client/issues/8365