You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if the user manually removes the tool's integration with Canvas from the Canvas side (in the user's Settings), then tries to reload CCM (or make an API call on a preloaded client), an error message will flash briefly before the user is redirected to the root (App.tsx) and then shown the authorize text (AuthorizePrompt.tsx). This is because an UnauthorizedError is ultimately thrown, but the redirect (window.href = '/') takes a couple moments to take effect. This can be somewhat confusing to the user, though ultimately it shouldn't hamper their use of the tool.
Unfortunately, because the redirect occurs in a plain JS/TS utility function, rather than a React component, it's not simple to change what the user sees without also modifying error handling, and making changes in many places.
One possible solution would be to delay a second or two after redirecting before resolving the function (handleErrors is async), which would likely hide the error, though the user may see loading content flicker.
Screen.Recording.2022-03-29.at.5.13.09.PM.mov
The text was updated successfully, but these errors were encountered:
Currently, if the user manually removes the tool's integration with Canvas from the Canvas side (in the user's Settings), then tries to reload CCM (or make an API call on a preloaded client), an error message will flash briefly before the user is redirected to the root (
App.tsx
) and then shown the authorize text (AuthorizePrompt.tsx
). This is because anUnauthorizedError
is ultimately thrown, but the redirect (window.href = '/'
) takes a couple moments to take effect. This can be somewhat confusing to the user, though ultimately it shouldn't hamper their use of the tool.Unfortunately, because the
redirect
occurs in a plain JS/TS utility function, rather than a React component, it's not simple to change what the user sees without also modifying error handling, and making changes in many places.One possible solution would be to delay a second or two after redirecting before resolving the function (
handleErrors
isasync
), which would likely hide the error, though the user may see loading content flicker.Screen.Recording.2022-03-29.at.5.13.09.PM.mov
The text was updated successfully, but these errors were encountered: