Open GoogleCodeExporter opened 9 years ago
A supposed use of it would be
ErrorReporter.getInstance().handleException(caughtException); (default)
EventReporter.getInstance().sendInfo(infoParameters, target);
Original comment by sammyshe...@gmail.com
on 24 Jul 2012 at 1:32
There are actually 2 requests in your proposal:
- handling multiple forms, which could be interesting for many reasons
- reporting app usage stats
The second topic (stats) has been in my mind for a long time, and every few
months, I'm thinking about adding such a feature or not.
Usually I come to the conclusion that ACRA is all about reporting bugs. So I
don't go further towards stats.
But every time I check some ACRA reports, I am amazed by the potential value
that we could gain from using all these data for stats...
So, I might in some later version change my mind and add a statistics module to
ACRA, but doing it as a simple second formKey does not sound to me like the
right way to help devs with these stats. Collecting data is a simple matter.
Extracting key indicators from the data is complex. I've not really analyzed
anything on this topic, but I might start after I release ACRAv4.3... Hopefully
soon...
Original comment by kevin.gaudin
on 24 Jul 2012 at 10:19
About the multiple forms... This is something that should be possible with the
upcoming version 4.3. I modified the trunk yesterday to allow the handling of
multiple ACRAConfiguration instances which contain every ACRA configuration
items, including the formKey. So it should be possible to switch from one
config instance to another to post different data to different forms.
There might be some shortcomings though, like for example the handling of a
real Exception at the very moment where ACRA is configured to send a stats
report... you can expect pollution in your stats spreadsheet and loss of
reports in your crashes spreadsheet.
Original comment by kevin.gaudin
on 24 Jul 2012 at 11:32
Original issue reported on code.google.com by
sammyshe...@gmail.com
on 24 Jul 2012 at 1:14