Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Email not working?

See original GitHub issue

Issue Description

I just added ACRA to our project and placed some invalid code in startup to make it crash. I added ACRA’s “Toast” component and the “Email” component. The toast message shows, however no email is ever sent. I check the debugger and it says something like unable to start service Intent {AttachmentService} not found. I followed the directions in the wiki: any idea what I am doing wrong? I’m on an Android Pixel device and the AndroidManifest has the INTERNET user permission set, if that helps.

Issue Analytics

State:
Created 4 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

Sean-Brown-Digicommented, Nov 29, 2018

That’s really good to know and you are right, ~~I put the crash in onCreate() and ACRA handled it correctly~~. Previously I put the crash code in attachBaseContext() and I would only see the toast message but not get any email dialog.

EDIT: I take that back, putting the crash in onCreate() only shows the toast message, but no email dialog.

1reaction

F43nd1rcommented, Nov 29, 2018

I put the crash code later in the program’s execution and it opens the email program properly

Good to know that it works.

during my testing I put in code which caused the app to crash right after ACRA.init()

Acra will retry to send reports on the next launch. Which means unless the application start crashes every time, reports will reach you eventually. If the application start crashes every time, there is no way to get the report out anyway.

I assume because the MainApplication wasn’t fully created before the crash

Acra might even be able to catch crashes in Application.onCreate, but I’m not sure on this. It will catch crashes in Activity/Service startup, where initialization of your app should be.