Skip to content
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

Handle ChunkLoadError #1250

Open
5 tasks
smadbe opened this issue Dec 23, 2022 · 0 comments
Open
5 tasks

Handle ChunkLoadError #1250

smadbe opened this issue Dec 23, 2022 · 0 comments
Assignees

Comments

@smadbe
Copy link
Contributor

smadbe commented Dec 23, 2022

Overview

Several times per week, we get notified of users who get a crash of the app on a ChunkLoadError because of an app caching issue, an CDN failure or just a deployment which happens at the same time as the user enters the apps. (you can find many blog posts discussing this online)

We cannot do much about this issue but we can suggest the user to reload the app.

Acceptance criteria

  • Make sure you can reproduce it (and explain the reviewer how he can as well)
  • In the error handler, when you have an error message matching /Loading chunk [\d]+ failed/, display a fatal error such as those already handled in the app component. As a message, in this case, write "The application has been updated since you opened it, it needs to be reloaded."
  • Modify the "Try to refresh the page" to a button which cause the browser to reload the app. Use as label "Reload the application." (for any fatal error)
  • Improve a bit the style of this. Center the message? Center the button ? Center "If the problem persists, please contact us." in a smaller font?
  • Todo @smadbe only? Test if it works when the user arrives through LTI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants