-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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 ReactDOMServer does not yet support Suspense #8200
Comments
Hi @jamesgrogantech thanks for writing in!
This looks oddly familiar to #8216. We'll need to investigate what happens here, which param is undefined and why. Perhaps Remix changed something around building/bundling recently 🤔 I have to backlog this though as we're currently swamped with other issues. We'll try to take a look at this soon. Any help would be greatly appreciated in the meantime :) |
Hi @jamesgrogantech, thanks for the issue report.
I suspect this issue might be caused by incompatible React and Remix versions, as Remix 1.16.0 uses Do you only see this error when Sentry is used? If so, could you create a reproducible example please? Thanks! |
I've managed to solve this through a fix for an unrelated bug happening due to multiple calls to redirect during authentication. I'm not sure on the exact cause of the issue, but I have moved to using a single "/login" route to call my authentication to redirect to Microsoft SSO rather than calling this redirect from multiple loaders at once. This seems pretty unrelated to the Sentry error but I have confirmed this change has fixed it so I hope it helps someone else if they come across the same thing. |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/remix
SDK Version
7.53.0
Framework Version
React 17.0.2, Remix 1.16.0
Link to Sentry event
SDK Setup
entry.server.tsx
Steps to Reproduce
Sentry.init
to the entry.server.ts fileExpected Result
I expect Sentry to not interfere with the request handler.
Actual Result
I get this error when I make a request to the application:
I am not using Suspense anywhere in the application.I am using Sentry in the client with no issues at all, but as soon as I add it to the server I get this error.
I tried to turn on the Sentry Debug and got this warning at the same time so I wonder if it's related:
Sentry Logger [warn]: Remix SDK was unable to wrap your root because of one or more missing parameters.
There is discussion about this particular warning here #6951, but they don't seem to be experiencing the Suspense error.
Any help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: