Component set in the errorElement prop on Route is not being displayed on load error about location

[tannerlinsley]

Definitely a bug. I’m on it.

…

On Nov 21, 2021, 8:07 PM -0700, fetters5 ***@***.***>, wrote: Describe the bug the component set in errorElement is not being displayed when an error occurs in the loader function. This also happens with the defaultErrorElement To Reproduce Steps to reproduce the behavior: 1. Go to (https://codesandbox.io/s/gracious-river-qy27x?file=/src/index.tsx:768-777) 2. Click on the Posts link 3. See ugly error in sandbox instead of the expected nice error Expected behavior I would expect it to render the ErrorTest component in the sandbox. This also fails locally for me Desktop (please complete the following information): • OS: Windows • Browser: Chrome • Version: 3.28 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[JoshuaAmaju]

This might be related to the issue I've been having in trying to integrate React Location with React Native. Hopeful the fix should solve that for me.

[larsvankleef]

Don't know if this is related, but when showing the pendingElement and the request fails or takes longer than the timeout time set in the router, the pendingElement stays visible. Instead of the errorElement of the defaultErrorElement

[fetters5]

If instead of throwing you return a promise rejection it works the first time. I cannot get even this to work in the sandbox though.

In my case my bad router is"/bad" and the first time I go to "/bad" it will respond with the error element, if I go to another route and try to go back to "/bad" it will just hang as if in a pending state

[fetters5]

@tannerlinsley I narrowed the issue down to a rejectLoader call and submitted a PR, if I am way off base let me know but this fixed my issues with error elements

[tannerlinsley]

Should be fixed!