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
Right now, we handle most exceptions in a fairly user-friendly way(ones that may occur during transpilation process and in redux thunks).
But some lead to "crash to the gray screen", not giving a user any error messages or even a chance to save currently opened project(like #1468). Those exceptions are caused by a combination of current state and some bug in selectors or rendering code. In that case, we can't just try rendering the same thing again, because that would lead to the same exception.
But instead of rendering nothing, we can provide some recovery options
export current changes to a .xodball
undo last action and try rendering again
simulate opening project in the current state(that could help if crash was caused by some complex UI manipulations)
The text was updated successfully, but these errors were encountered:
Right now, we handle most exceptions in a fairly user-friendly way(ones that may occur during transpilation process and in redux thunks).
But some lead to "crash to the gray screen", not giving a user any error messages or even a chance to save currently opened project(like #1468). Those exceptions are caused by a combination of current state and some bug in selectors or rendering code. In that case, we can't just try rendering the same thing again, because that would lead to the same exception.
But instead of rendering nothing, we can provide some recovery options
.xodball
The text was updated successfully, but these errors were encountered: