Hello Android Devs ! Here comes a new major version of ACRA. For those who do not know ACRA (Application Crash Reports for Android), this is an opensource (Apache licence) library allowing your application to send crash reports to a simple Google Docs spreadsheet. You should go to the project home page to read more about its features: http://acra.googlecode.com
The main motivation of that new version was to get rid of the need of subclassing an ACRA-specific android Application class. This previous requirement was preventing developers from using both ACRA and other feature-rich libs/frameworks like GreenDroid (https://github.com/ cyrilmottier/GreenDroid), RoboGuice (http://code.google.com/p/ roboguice/), Droid-Fu (https://github.com/kaeppler/droid-fu) and others. This goal has been achieved by moving the configuration of ACRA from overridden methods to an ACRA-specific annotation: @ReportsCrashes. While reaching the goal of allowing to inherit from any Application subclass, it also makes the process of integrating ACRA to a project even easier. Here is the look of an application class using ACRA with Toast notification mode: @ReportsCrashes(formKey = "dEhuSldocldoUDazR25jM2dtSGo2QXc6MQ", mode = ReportingInteractionMode.TOAST, resToastText = R.string.crash_toast_text) public class CrashTest extends Application { @Override public void onCreate() { // The following line is required to initialize ACRA ACRA.init(this); super.onCreate(); } } Isn't it cleaner? As we were going to release a new major version, we also added some useful data to the reports: * The details of the device Configuration at its initial state when initializing ACRA. 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 we are sure you'll find this useful. * The details of the screen size and density * The local date/time of the crash The new version now needs to be fully tested before being declared stable. Please follow the instructions in the updated How-To (http:// code.google.com/p/acra/wiki/ACRA3HowTo) to install it in your application project and file issues in the issue tracker: http://code.google.com/p/acra/issues/list All your comments, questions or feature requests are as always welcome, please do not hesitate to contact me! Kevin -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
