Closed Ereza closed 11 years ago
In the acra-storage database, the recent-items
view creates keys with a call to new Date(doc.USER_CRASH_DATE)
.
The USER_CRASH_DATE
you got in this report is invalid: 2013-05-17T16:16:01.000+561930:14
and can't be parsed by Javascript. The timezone +561930:14 is... strange. The USER_APP_START_DATE
is correct though.
I won't just patch it to omit the timezone if the crash date is malformed. This would be a too specific workaround for one special case.
One thing I can do however is use the crash reception date (timestamp
field) generated by acra-storage if the report crash date parsing fails.
Here's what I did:
USER_CRASH_DATE
when report is submitted and replace it with server-side generated timestamp if not valid. A special flag USER_CRASH_DATE_FIXED_BY_ACRALYZER
is set to true to let you know that the date is not what was submitted.USER_CRASH_DATE
, test that its value is valid and replace it with timestamp if not. This will let older corrupted data be usable anyway.I pushed the fix on the master branch of ACRA/acra-storage. You can update your acra-storage instance(s).
I confirm it now works correctly. Thanks for the fix and all your hard work on Acralyzer! :)
I am using ACRA+Acralyzer for my projects, and I have received a report which is crashing Acralyzer views (if I try to browse reports, and this report is on the list, I just get the loading image with the bug icon).
Maybe it has something to do with the report being from the BlackBerry runtime for Android, or with the strange dates it has (uptime is also strangely null).
Watching the page response from Acralyzer from the browse reports page, I can see that this report has a "null" key:
I attach the full report (extracted from Futon) here: