Implement crash handling / error reporting
See original GitHub issueDetails on the idea can be found here: https://forum.blockstack.org/t/proposal-opt-in-error-reporting-for-the-browser/5890
Technical implementation should be a componentDidCatch
handler on the top level app component to render when an uncaught error bubbles up. For error reporting, I’d suggest making a new browser-api.blockstack.org
endpoint to send an error to https://sentry.io/for/node/ that strips out identifying information (e.g. IP address.)
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
The complete guide to error monitoring and crash reporting
Integrating crash reporting into your Slack, Teams or other chat tool is a great way to ensure the team sees issues and can...
Read more >Part 3: sending crash reports to an error reporting API - Bugsnag
Part 3 of everything you ever wanted to know about error handling on Android - sending crash reports to an error reporting API....
Read more >4 Best Error and Crash Reporting Tools for 2022
Error and crash reporting tools help identify and diagnose the root cause of a crash so you can find the right solution for...
Read more >Strategies/techniques for crash reporting in Java
All you do is create a external program that does the error reporting and then use the JVM option to send the core...
Read more >Customize your Firebase Crashlytics crash reports - Google
You can associate arbitrary key/value pairs with your crash reports, then use the custom keys to search and filter crash reports in the...
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 FreeTop 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
Top GitHub Comments
Comment from the issue I’m about to close:
We want to prototype some kind of automatic exception tracking in the Browser. This will help us catch and diagnose issues without users having to reach out to us with a backtrace.
There are complications related to the Browser:
The work here will be to prototype something, make sure it fulfills the requirements, test it, and then potentially release.
@hstove Sounds great, thanks for pushing this forward quickly 💪🏻