9ba0bc831c
Catch possible exceptions when creating the fileName
...
This can apparently happen, and we should have a fallback. Additionally
Dart has both an 'Error' and an 'Exception' which are two different
things. This makes no sense.
2020-06-09 18:09:17 +02:00
b9b53f28c4
Log some exceptions are warnings
...
These aren't really a problem, but it's still interesting to know if
they are happening.
2020-05-31 02:00:00 +02:00
49bf02bf15
logEvent: Parameters must be <String, String>{}
...
Not string, dynamic. Sentry wants strings.
2020-05-01 10:50:09 +02:00
2494f3af8f
ErrorReporting: Not all Errors are exceptions
2020-05-01 09:12:18 +02:00
c0623d1c3c
Sentry: Add error breadcrumbs
...
This way we will have some context as to why an error happened.
2020-04-22 01:31:32 +02:00
6c47016c8b
logException: Also log to Sentry
2020-04-17 09:42:19 +02:00
fd7ad7d92b
Generate a random uuid for each user for Sentry
...
This way, we know if one particular user has lots of errors. Firebase
Crashlytics used to do this automatically, I think.
2020-04-16 11:49:20 +02:00
e426f5523c
Do not report Flutter errors to Crashlytics
...
It's just extra noise. We're still initializing it as I want the
iOS/Android level errors.
2020-04-14 16:19:44 +02:00
ed5e86cf83
Get Sentry DSN from env variable
2020-04-10 12:10:37 +02:00
7e0b073f32
Move error reporting to its own file
...
* Avoid passing Flutter errors to its Zone handler, this doesn't always
catch the errors
* Catch the current isolate's errors. I haven't been able to test this
out, but lets see.
2020-03-30 11:20:04 +02:00
