Crash reports written by Acra-3.1.1 or prior will cause a later version of Acra to crash

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Cause an App using Acra-3.1.1 or prior to crash and write a crash report.
2. Redeploy the app with a version of Acra after Rev#250 (ie Acra3.1.1+ or 
3.2.0) without wiping the app data.
3. Start the app and you will see a notification of an Exception (from within 
Acra). The original crash report will not have been sent (and will never be).

What is the expected output? What do you see instead?

You should probably only see a warning/error in the log that Acra could not 
read the crash report. But you also see the unhandled notification Toast. And 
it will recurr each time the app is started.

What version of the product are you using? On what operating system?
Acra-3.1.1 on an emulator running Android 1.5 where I saw another similar crash 
report reading error that looks like was made irrelevant with Revision#250. But 
in tracking it down I can copnfirm that this error will occur in future 
versions of Acra.

Please provide any additional information below.

I have attached a patch that I believe will mitigate the problem caused by old 
crash reports.

Original issue reported on code.google.com by william....@gmail.com on 21 Mar 2011 at 1:28

Attachments:

• Safely_handling_crash_reports_written_with_an_oldversion.patch

[GoogleCodeExporter]

Applied your patch in rev 323. Thanks!

Original comment by kevin.gaudin on 21 Mar 2011 at 10:50

• Changed state: Fixed

[GoogleCodeExporter]

Glad I could add something back.

Original comment by william....@gmail.com on 21 Mar 2011 at 11:13

[GoogleCodeExporter]

Original comment by kevin.gaudin on 22 Dec 2011 at 9:08

• Changed state: Verified