-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
checkError can have undefined error as parameter #9845
Labels
Comments
Hi, and thanks for your report. We need a reproduction to investigate on this bug. Can you please tweak the simple example (link below) and post a link to your modified sandbox? https://stackblitz.com/github/marmelab/react-admin/tree/master/examples/simple?file=README.md |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since a couple weeks we get the behavior that if we access the root address of our react-admin application it gets stuck on loading because in the AuthProvider a new behavior appeared: the
checkError
method can have an undefinederror
as input parameter.According to the docs this is not intended as shown in the example implementation: https://marmelab.com/react-admin/AuthProviderWriting.html
Was there a change on how the AuthProvider
checkError
is being used?Steps to reproduce:
Use the example AuthProvider implementation and call the root address.
This fixes the problem, but it feels a bit weird.
Additionally, there seems to be a related issue on some internal code called
Retryer
where theonError
function also acts on an undefinederror
input parameter as well as theuseQuery
call with theauth/getPermissions
key wants to act on an undefinederror
while handling it in theonError
method.Environment
The text was updated successfully, but these errors were encountered: