App Route's Error.tsx is not working for SSR routes.
Unanswered
American Oystercatcher posted this in #help-forum
American OystercatcherOP
I am having an issue with error.tsx file with error handling.
Once I added that special file, I started getting this error.
And lots of warning messages with this.
And when I click the link (or button to navigate to other page), It showed white screen with the same route. (Does not go to the route it has to be)
This time, it showed these errors.
Do you have any idea on that?
P.S: This happens only on SSR routes. It works fine on Client Side rendering routes.
Once I added that special file, I started getting this error.
TypeError: Cannot read properties of null (reading '_pendingVisibility')And lots of warning messages with this.
Warning: Unexpected Fiber popped.And when I click the link (or button to navigate to other page), It showed white screen with the same route. (Does not go to the route it has to be)
This time, it showed these errors.
The above error occurred in the <ErrorBoundaryHandler> component:Uncaught Error: Unexpected Suspense handler tag (undefined). This is a bug in React.fetch-server-response.js:64 GET http://localhost:3000/collection/2VLjompcdUoCM0PwgE8kHb9Q79M?_rsc=acgkz net::ERR_CONNECTION_REFUSEDFailed to fetch RSC payload. Falling back to browser navigation. TypeError: Failed to fetchDo you have any idea on that?
P.S: This happens only on SSR routes. It works fine on Client Side rendering routes.
2 Replies
American OystercatcherOP
Is there anyone who can give me an answer on this?
Ocicat
@American Oystercatcher Hey man, did you find a fix for this? I have the same issue