HmadaAhmedSalem / geobeagle

Automatically exported from code.google.com/p/geobeagle
0 stars 0 forks source link

Sync fails parsing xml #214

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Download a pocket query
2. Transfer to /sdcard/downloads/
3. Use GeoBeagle menu -> Sync option

What is the expected output? What do you see instead?

Expect sync of caches.
Get "Error parsing file '/sdcard/download/nnn.gpx: PI must not start with xml 
(position: unknown @1:5 in java.io.BufferedReader@432a5e08)'.

What version of the product are you using? On what operating system?

Latest downloaded 1.Mar.2012 on T-Mobile G1 Firmware 1.6

Please provide any additional information below.

Original issue reported on code.google.com by rmjh...@googlemail.com on 1 Mar 2012 at 2:46

GoogleCodeExporter commented 9 years ago
Can you attach the xml file?

Original comment by step...@theleengs.com on 1 Mar 2012 at 3:43

GoogleCodeExporter commented 9 years ago
Seems to be happening with all mine today. I've attached the smallest.

Original comment by rmjh...@googlemail.com on 1 Mar 2012 at 3:53

Attachments:

GoogleCodeExporter commented 9 years ago
Looks like geocaching.com changed the XML file format.

This thread explains it and a temporary workaround - 
http://forums.groundspeak.com/GC/index.php?showtopic=290672

Original comment by robneil...@gmail.com on 4 Mar 2012 at 7:14

GoogleCodeExporter commented 9 years ago
Thanks for the pointer.

Original comment by rmjh...@googlemail.com on 4 Mar 2012 at 7:50

GoogleCodeExporter commented 9 years ago
my two cents:
There are a few posts of Moun10bike like this in the forum:
" This is possibly due to a byte order mark (BOM) that was added to the start 
of GPX files in the February 14th release. We will be removing those characters 
in the March 13th release, but until ..."
So, be patient until March 13th (two more days) and hope that they will fix it.

Original comment by AgileN...@googlemail.com on 11 Mar 2012 at 4:12

GoogleCodeExporter commented 9 years ago
Thanks. That will work for me. Glad they're fixing their problem. :)

Original comment by rmjh...@googlemail.com on 11 Mar 2012 at 7:40