Hi, fellow Android applications developers,

Here is an update on the ACRA project. (See http://acra.googlecode.com)

For those of you who would not know ACRA, this is an open source
library under Apache license allowing your application to send crash
reports to a Google Spreadsheet. Works on all android versions (tested
from 1.5 to 2.3), without any requirement of publishing your app on
any market.

After a few months of tests, we published a new stable version of
ACRA. Labeled 3.1.0, here are the major changes:

- ACRA's configuration is now done through an annotation attached to
your application class. You don't need to inherit from any specific
Application subclass anymore. This means that you can now use ACRA
with any other rich featured framework like GreenDroid, Droid Fu or
Roboguice which have their own specific Application subclass
inheritance requirement.

- We also added some useful data to the reports:
  * The details (and in a human readable flavour) of the device
android.content.res.Configuration at its initial state when your
application starts . This includes the user locale (language/country),
his Mobile Country Code and Mobile Network Code, the type of available
input methods (keyboard, navigation, touch...), screen orientation
(landscape/portrait)...
  * The same Configuration data but at the moment of the crash. This
can allow to track issues due to Configuration changes like opening/
hiding physical keyboard, changing orientation... These issues are
often hard to understand and I'm sure you'll find this useful.
  * The details of the screen size, resolution, density, refresh
rate...
  * The user local date/time of the crash

- A Wiki page has been created to help you configure ProGuard to work
with ACRA : http://code.google.com/p/acra/wiki/ACRAProGuardHowTo
(thanks to pingrys!). Please feel free to add your comments to improve
this doc and help debugging applications using ProGuard.

What's coming next ?

The next version should be available "in the few following weeks" and
will allow you to include in crash reports:
- contents of the main logcat
- contents of the events logcat
- contents of the radio logcat
- contents of the dropboxmanager (maybe this could lead to future
works on using StrictMode API to report ANR issues ?)
- more data about the dalvik memory usage

We are still working on a potential way of providing a new Reporting
Interaction Mode which would be a direct Dialog (without status bar
notification). Though, this is a really hard work and can't plan any
ETA for the moment. (thanks go  to brainpilot!).

I hope this will help you to go further in improving your applications
quality and reduce your "platform fragmentation" headaches ;-)

All comments and new ideas about ACRA are welcome !

I wish you all the best for the few last days of 2010 and beyond,

Kevin

Kevin

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to