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

Support surfacing non-fatal errors more aggressively in test builds #84

Open
nbrooke opened this issue Feb 18, 2021 · 0 comments
Open

Comments

@nbrooke
Copy link
Member

nbrooke commented Feb 18, 2021

Right now crash / error reporting is either turned off in test builds (if we are using something more invasive like BugSee) or just report normally (which might not be supper useful if interesting new errors are just appearing in the general set from production). There are some things we can do to improve the current situation (#72, #83), but there are also other things we could do to make non-fatals in that environment MORE obvious.

For example showing an onscreen popup of some kind any time a non-fatal happens, with an immediate option to send detailed logs, maybe trigger a BugSee event if it's active, etc.

This would make it more likely to catch serious problems that don't cause visible bugs when they happen immediately, and up our chances of getting more useful error reports from internal or client QA.

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

1 participant