Closed kekonn closed 1 year ago
Thanks for the bug report. Could you provide an example track so I could try to reproduce the issue? Or at least a sub part of a track which contains a problematic date?
Sure, I think this is the specific track it's struggling : https://gist.github.com/kekonn/cc516d9b646d4845718ba051bea50a48
Incidentally, because it couldn't parse this one track in the entire folder, it wouldn't show any track in that folder. So it seems that the error handling could be a bit more robust.
Thanks. Pretty clear incorrect time format in your file.
<time>2022-03-27T15:32:37.504+02:00[Europe/Brussels]</time>
is definitely not supported by the GPX specs (and any date parser I know :grin:). Did you get this file directly from Calimoto or was it processed by something else?
Anyway I made the track process safer and made it work in your specific case so your track will have point times (and full stats).
Could you try v5.0.6-1-nightly? If not, v5.0.6 will come soon anyway.
I got this from someone else, but I guess it was directly recorded with calimoto. I thought it was a funny way of noting the timezone.
Question: I looked in the apps interface on my nextcloud instance, but I couldn't find a beta/nightly channel or anything. How do I install the nightly version?
Same procedure as github.com/julien-nc/cospend-nc#nightly After having tested it, as there is no database migration, going back from the latest nightly to v5.0.5 will work just fine.
I tried it with the nightly version and that fixed the problem, thanks!
Thanks for the feedback. v5.0.6 is out
The error:
I am on the latest version op GpxPod (5.0.5).