Display error messages on app startup for non-dev users
See original GitHub issueThe Issue
End users should have the ability to view whatever error caused the app to crash.
I will have one of the installed binaries fail to start and don’t know what the issue is, and since the developer tools are disabled, I can’t figure it out on my own. Back in the 2000s, applications would just give you an error message or error code so you can debug it. The lack of this ability removes the end user’s ability to debug it, or our ability to prevent it.
Steps to Reproduce
Expected Behavior
Error messages should be displayed to the user
Actual Behavior
Error messages are not displayed to the user.
Suggested Solutions
alert(error);
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
How to Write Helpful Error Messages to Improve Your ...
How to Write Helpful Error Messages to Improve Your App's User ... A generic error message displaying: "Oops, something went wrong.
Read more >Is there a good reason not to display error messages ...
An application should display an error dialog if there is a reasonable expectation that the user is waiting for the app; if your...
Read more >How to get users to read error messages? [closed]
Show them the message. Due dilligence and all, but log every error to a file. Users can't remember what they were doing or...
Read more >Solved: UI Action Display Error message
Solved: I want to make it so that when someone click on the UI Action Implement before the start time it gives them...
Read more >Error Message Guidelines - Win32 apps
The guidelines in this topic are intended to help you write clear error messages that are easy to localize and useful for customers....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I gotcha. I guess for a quick fix you could change the errorBoundary/view.jsx component to put the error on the page. Just so you can see it.
Gotcha, closing for now. Please reopen a new issue if there’s a particular action we need to take.