Closed 0x4f53 closed 1 year ago
@4f77616973 please add [Keyspace-adroid-crash report] as an email subject prefix
@nimish-ks Done.
Just to confirm: ACRA is just enabled for this kind of crash reporting – i.e. the user is in full control what is sent and no data leaves their system without their approval? And that's how it will stay? I just need to know as my updater just alerted me to set the Tracking
flag on Keyspace as it detected the library. If you can confirm the above (and to a non-dev like me the code in this PR looks that way), I'd instead white-list ACRA for your app.
Just to confirm: ACRA is just enabled for this kind of crash reporting – i.e. the user is in full control what is sent and no data leaves their system without their approval? And that's how it will stay? I just need to know as my updater just alerted me to set the
Tracking
flag on Keyspace as it detected the library. If you can confirm the above (and to a non-dev like me the code in this PR looks that way), I'd instead white-list ACRA for your app.
@IzzySoft Yes that is correct. We only use ACRA when the app crashes. You will be prompted with a dialog to optionally send crash logs, and if you chose to do so, your phone's default email app will be used to create an email with the logs as an attachment.
Great, thanks! Then I'll now white-list ACRA for your app instead of (unnecessarily) raising the Tracking flag. Wonderful!
:recycle: Current situation
Crashes always happen ungracefully. Users often need to report them by replicating them, copying them and pasting them into ADB. This is lame.
:bulb: Proposed solution
Implement easier, dialog-based, crash log emailing. This works as such:
📚 Release Notes
Library version bumps
androidx.appcompat:appcompat
1.5.1 -> 1.6.0androidx.test.ext:junit
1.1.4 -> 1.1.5androidx.test.espresso:espresso-core
3.5.0 -> 3.5.1📝 Testing
Exception()
class.