Date = 12/31/0000 and no version name

[jsalatiel]

Why can't i get the version number or date of the report?

My reports shows no date or version name.
See this:

It also overlaps package name and exception

[gen2brain]

Hi, frontend part of this project was just me trying to use modern frameworks like Vue, but actually never did use something similar before. All PRs that can improve that are welcomed, e.g. multi select and multi delete etc. it can be improved in many ways, and it is just a simple index.html file.

As for question why there are no dates or versions, I don't have the answer. I do have live app with acra-go reports backend, that receives many many similar strange data. Some devices behave strange, some work in undefined ways, some don't send any data at all except the name of device. I am not sure how to fix that, but all suggestions are welcomed.

[lidongzhuo]

Same reported time issue.

I review http://xx.xx.xx.xx:55000/view, the returned data did are those.

So as you said, is this the bug of acra?

[Kbungo]

Not an ACRA bug. I don't know if Acra has changed it's report format, but as of ACRA:5.2.0, the report format is:
"2018-10-04T15:58:21.678-07:00"
and is coming in normally in the HTTP Request.
Post serialization to a Report object in code it comes back as different incorrect values.

The serialize also drops ALL logcat data and about 90% of other data from ACRA.

I only know enough golang to figure this out. no clue how to fix it and no intention to try. Just want to leave this info here so a future developer can update the object and it's serializer to convert correctly. (Sorry)

EDIT: It appears that using a minimized version of the crash data will return the correct time. Here's the ACRA annotation I'm using that'll return it.

@AcraCore(buildConfigClass =  BuildConfig.class,
        reportContent = {
                REPORT_ID, APP_VERSION_CODE, APP_VERSION_NAME, PACKAGE_NAME, PRODUCT, ANDROID_VERSION,
                BUILD, TOTAL_MEM_SIZE, AVAILABLE_MEM_SIZE, BUILD_CONFIG, STACK_TRACE, DISPLAY, USER_CRASH_DATE
        })

I'm pretty sure that it's still an acra-go issue though, because that data makes it to the server. There's just some value in there that's causing the parser to barf.