apps-android-commons Organizing crash/bug reports (ACRAlyzer?)

We currently get most of our crash reports at https://groups.google.com/forum/#!forum/commons-app-android , since that's where the crash report function in the app sends them. Currently, when I want to address a crash report, I copy/paste it to GitHub so it can be discussed and marked 'done' when complete. But there are two downsides to this: (1) duplication of effort/content, and (2) now looking back at the crash report threads, it takes a bit of wracking the brain to remember which ones have been handled and which ones haven't. With more collaborators this might get more difficult.

Do you guys think there might be a better way?

Jun 16 '16 02:06 misaochan

You're totally right. We would gain a lot from using ACRA+ACRAlyzer https://github.com/ACRA We would need a server, I guess we could use a Labs instance for that.

Jun 16 '16 03:06 nicolas-raoul

Oh, cool. We seem to already be using ACRA (it's in the external libraries), so we just need to set ACRAlyzer up, right?

Jun 16 '16 05:06 misaochan

ACRA can be set up to send crashes directly without going via email. Not sure whether ACRAlyzer can deal with emails. As an example, AnkiDroid uses ACRA+ACRAlyzer without email: https://github.com/ankidroid/Anki-Android

Jun 16 '16 05:06 nicolas-raoul

Is ACRA something we can pull across (code) from Anki-Android? Do we still need to implement the proposal/ suggestion?

Chris.

Dec 17 '24 21:12 chrisdebian