Hey,
i don't recall the exact wording of the error message, but I recently recorded a track with OSMAnd+ v.4.2.7 on my Android phone (I'm upgrading to 4.3.5 just while writing this) and tried to import the resulting GPX-File in viking v.1.10 to process it further.
Viking says it cannot import the GPX file because it is of invalid format or a similar error message. I'll try that again with the updated OSMAnd and report the exact error message later this week
I opened the offending wih a text editor to check if It was corrupted, but I didn't see anything that jumped to my eye. I'll investigate that further.
My Plan is to re-import those recorded and "retouched" tracks to OSMAnd for my nightly deliveries in the future.
I've added the offending GPX-File to this ticket.
While I'm investigating this problem further I'll add my findings here.
I just tried to open the file with GPSPrune and that also fails. It looks like viking is innocent here, and the Bug Report belongs to OSMAnd...
Next I'll record a shorter track with OSMAnd and export that to work on that with viking and/or gpsprune. Maybe I damaged the file myself, and this isn't a bug at all...
Did you post the whole file you are using? When I downloaded it to inspect it, I got 81,920 bytes, but the data cuts off in the middle of a trackpoint (file line 2658). Definitely a bad GPX file.
Yes, what I uploaded, was the file I got, but I didn't look at the end of the file like you did. Thanks for the clarification. :-)
After cross-checking I am now sure that it is an OSMAnd Issue, so this ticket can be closed.