The following is the first few sections of a chapter from The Busy Coder's Guide to Android Development, plus headings for the remaining major sections, to give you an idea about the content of the chapter.

Crash Reporting Using ACRA

When you wrote your app, you intended for it to work.

Alas, the road to a very warm place is paved with good intentions.

Hence, it is fairly likely that your app will crash in the hands of your users. In order to be able to fix the underlying problems, you need to learn about the crashes and the state of the app at the time of the crash.

There are any number of solutions to this problem. This chapter will outline a few of them and focus on one open source solution: Application Crash Reports for Android, better known as ACRA.

Specifically, this chapter covers ACRA 5.1.1. If you used ACRA previously, the configuration API has changed a fair bit, particularly in terms of the annotations that you can use.


Understanding this chapter requires that you have read the core chapters and understand how Android apps are set up and operate. Having read the chapter on notifications is also a good idea, though not absolutely essential.

What Happens When Things Go “Boom”?

The preview of this section is out seeking fame and fortune as the Dread Pirate Roberts.

Introducing ACRA

The preview of this section was traded for a bag of magic beans.

Where ACRA Reports Crashes

The preview of this section was stepped on by Godzilla.

ACRA Integration Basics

The preview of this section is presently indisposed.

What the User Sees

The preview of this section was fed to a gremlin, after midnight.

What You See

The preview of this section apparently resembled a Pokémon.

ACRA and Processes

The preview of this section left for Hollywood to appear in a reality TV show.