Crashes reporting

[kirillt]

Crashes should be reported automatically, this will save time for extracting logs.
This setting must be configurable in settings menu (#77) and be enabled by default for debug builds and disabled for production.

[kirillt]

This library might be good https://github.com/ACRA/acra
Alternatives must be considered too. Maybe we will be fine with just sending e-mail with crash log.

[kirillt]

Release build must spawn email app with pasted crash log and our e-mail as the recipient.
Debug build must contain tiny email sender dependency and send report automatically.

[salihyalcin]

Hi, can I ask one question regarding crash reporting? As far as I understand from the requirements, are you good with using Firebase Crashlytics? The more app has users, the more emails need to be sent. I think solving this problem in a clever way would be with a service that provides crash reporting. I don't know maybe you have some concerns regarding privacy but I recommend firebase for this issue.

[kirillt]

@salihyalcin We have considered Firebase Crashlytics for this, but yes, here is the privacy concern. The app's purpose is to work with local files mostly (although remote resources might be added later). Hence it's possible to have zero internet connections for the app's work and this is security bonus.

I think also that to send e-mail is the easiest sane way to solve the problem. Also the app will be checked later to be able to work without Google Services and I guess they are necessary for Crashlytics.

[kirillt]

Also a button "send current log" would be useful for debugging purposes. Sometimes it's really annoying to connect cable.