Disabled/enabled states don't work correctly

GoogleCodeExporter commented 8 years ago

The options to enable and disable ACRA are a mess.

First of all, there's no direct way to query ACRA to see if it's enabled or 
not, so that when you directly call 
ErrorReporter.getInstance().handleException() an error will be handled even if 
ACRA is disabled.  ErrorReporter.enabled is not exposed with an accessor to 
query.  As an alternative, ErrorReporter.handleException() could simply ignore 
the request if it's disabled.

When changing enabled or disabled using preferences, disabling ACRA will call 
disable() on ErrorReporter, which sets the ErrorReporter.enabled field.  When 
enabling, though, it calls ACRA.initAcra which does not do anything that 
changes the ErrorReporter.enabled flag.

Original issue reported on code.google.com by aviche...@gmail.com on 26 Aug 2011 at 1:55

GoogleCodeExporter commented 8 years ago

Original comment by kevin.gaudin on 2 Jan 2012 at 8:51

Changed state: Accepted
Added labels: Milestone-Release4.3

GoogleCodeExporter commented 8 years ago

Original comment by kevin.gaudin on 7 Sep 2012 at 9:31

Changed state: Verified

jinwook1469 / acra

Disabled/enabled states don't work correctly #69