Import of Shearwater Dive Files (.xml format) - some dives generate error

Hello,

I'm trying to use the Shearwater Dive Files (.xml format) import function on Garmin Connect Web (Activity-> all activities -> imnport).
While some of the dives import just fine, I have trouble with roughly half of all as the website throws this error: An error occurred with your upload. Please try again.

I have tried to compare the XML files to see if there are any obvious issues, but was not successful.
If Garmin support could please reach out to me so I can share 2 XML samples - one working, one throwing the error for you guys to troubleshoot the issue?

Thanks !

  • If Garmin support could please reach out to me so I can share 2 XML samples

    It is uncertain it happens here, on the user forum, but you can zip and post the files here (see the Insert » Image/Video/File function), so that others, experienced users, can have a look at it. Otherwise, you can also contact the Support directly at https://support.garmin.com

  • Update: Managed to get it to work. Turns out Shearwater XML file seems to follow the system settings or the rest of world date format when exporting XML logs (I tried to change the format in the app but that only seems to change the way the date is displayed in the app).

    Garmin import is based on the US month first format (us Europeans will never understand that Rofl) so I had to manually edit each xml file to flip month and date around (each of my xml files had 2 such entries, find and replace made quick work of it).

    With this I was now able to Import all my old dives (old dive computer - > Subsurface - > Shearwater - > Garmin) to Garmin dive.

    Hope this helps someone looking for a similar solution. 

    P. S. Full workflow how to do it here: scubaboard.com/.../post-10682418

  • Add on to above: max import 4 dives at a time vis garmin connect web. If more are imported, the garmin db or syn between connect and dive fails and you end up with dives you can't edit or view on garmin dive.

    If thay happens only solution is to delete that dive on garmin dive and re-import in batches of max 4 at a time)