“Uploaded to OpenStreetMap” always reported as “1 Jan 1970 01:00:00”

[Lee-Carre]

OSMtracker v1.0.1 on Android v10 on SM-A405FN

When uploading a GNSS trace, the date & time of said upload is always reported (within OSMtracker) as the Unix epoch (plus one hour (perhaps because of being on BST as opposed to GMT, currently)).

This is true for all uploads, consistently.

The OSM site itself reports the correct date & time of those same uploaded traces.

[Lee-Carre]

Additionally, the notation displayed in the UI doesn't follow the standard notation of ISO 8601.

[jamescr]

I found this issue on one trace but not in all uploads.

Can you provide a screenshot of the place were you see the wrong date?

[Lee-Carre]

Apologies for the (long) delay in replying.

The highlighted location in your UI-capture is where I see the incorrect date & time with my own traces.

If still needed I can upload my own example.

Thankyou for your attention in this. I have stopped uploading traces which I capture, to avoid contaminating any other uploads, until an update is available. Despite being in an area with a severe lack of tracings.

I've had a think about why only some of yours are affected but all of mine are affected. I couldn't determine what might be causing the difference. My captures all vary in multiple ways (e.g. some short, some long).

[Andyporras]

Hello, @Lee-Carre.

Thanks for reporting this problem and for your patience. I am happy to inform you that the Unix epoch problem in GNSS trace dates has been resolved in PR #495. You can test this solution using the version corresponding to this PR.

If after testing it you notice any additional details or have any questions, don't hesitate to mention it, thanks again for helping us to improve OSMTracker!

Regards.

[Andyporras]

solved in the pr #495