Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remix and Apollo Client Devtools throw errors #122

Closed
SteaceP opened this issue Sep 27, 2022 · 3 comments
Closed

Remix and Apollo Client Devtools throw errors #122

SteaceP opened this issue Sep 27, 2022 · 3 comments
Labels
needs-response We need a response from the original author about the issue

Comments

@SteaceP
Copy link

SteaceP commented Sep 27, 2022

Have you experienced this bug with the latest version of the template?

Yes

Steps to Reproduce

Have Apollo Client Devtools installed on any of those browsers: Chrome, Edge, Firefox (all latest version as of today). With the Remix stack of course ...

Expected Behavior

No errors and SSR.

Actual Behavior

Seems to load entry.server.ts then fall back to entry.client.ts and you get all those errors in the browser console:

  • Error: Promised response from onMessage listener went out of scope
  • Uncaught Error: Hydration failed because the initial UI does not match what was rendered on the server
  • Error: Hydration failed because the initial UI does not match what was rendered on the server.
  • Uncaught Error: There was an error while hydrating. Because the error happened outside of a Suspense boundary, the entire root will switch to client rendering.

Deactivating the extension remove all the errors and SSR work

p.s. It happens on the 2 other stacks too. And sorry if the bug is actually from the Apollo devtool

@mcansh
Copy link
Contributor

mcansh commented Sep 29, 2022

looks like Apollo Devtools is modifying the DOM so React is throwing due to the difference between the server render and the client being hydrated.

@github-actions
Copy link
Contributor

This issue has been automatically marked stale because we haven't received a response from the original author in a while 🙈. This automation helps keep the issue tracker clean from issues that are not actionable. Please reach out if you have more information for us or you think this issue shouldn't be closed! 🙂 If you don't do so within 7 days, this issue will be automatically closed.

@github-actions github-actions bot added the needs-response We need a response from the original author about the issue label Apr 17, 2023
@github-actions
Copy link
Contributor

This issue has been automatically closed because we didn't hear anything from the original author after the previous notice.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-response We need a response from the original author about the issue
Projects
None yet
Development

No branches or pull requests

2 participants