New Releases - macOS 2.10.4, iOS 1.3.4

General MacDive discussion, updates, etc.
sbonzix
Posts: 2
Joined: Mon Feb 11, 2019 5:11 pm
Dive Computer: Aladin Sport Matrix

Re: New Releases - macOS 2.10.4, iOS 1.3.4

Post by sbonzix » Mon Feb 11, 2019 5:54 pm

nick wrote:Hi there,
I have just released a couple of new versions.

iOS 1.3.4:
  • Improved reading of UDDF files

    -nick
Hi nick,
when trying to import dive data to MacDive iOS from a uddf file generated by Diving Log 6.0.15 I get a "UDDF version 2.2.0 not supported" error message.
What version of UDDF is currently supported by MacDive/iOS?
Is there a way to convert between UDDF versions?

Thanks,
Stefano

User avatar
nick
Site Admin
Posts: 4016
Joined: Sat Apr 12, 2008 8:33 am
Dive Computer: Shearwater Teric
Contact:

Re: New Releases - macOS 2.10.4, iOS 1.3.4

Post by nick » Mon Feb 11, 2019 6:07 pm

3.x is supported.

Coming from Diving Log your best bet is to just export an sql backup file, which MacDive for iOS will read. I forget what changed from UDDF 2 to 3, and the website doesn't seem to list the spec any more.

sbonzix
Posts: 2
Joined: Mon Feb 11, 2019 5:11 pm
Dive Computer: Aladin Sport Matrix

Re: New Releases - macOS 2.10.4, iOS 1.3.4

Post by sbonzix » Mon Feb 11, 2019 9:06 pm

nick wrote:3.x is supported.

Coming from Diving Log your best bet is to just export an sql backup file, which MacDive for iOS will read. I forget what changed from UDDF 2 to 3, and the website doesn't seem to list the spec any more.
Thanks for your fast answer nick.
I've been trying with exports from Diving Log both as MySQL and SQLite dumps (the only sql options I can find in Diving Log), but none was accepted by MacDive iOS ("Failed to read from database").
Am I missing something?

Stefano

User avatar
nick
Site Admin
Posts: 4016
Joined: Sat Apr 12, 2008 8:33 am
Dive Computer: Shearwater Teric
Contact:

Re: New Releases - macOS 2.10.4, iOS 1.3.4

Post by nick » Tue Feb 12, 2019 3:24 am

The sqlite option should be correct. Send me the file, I will take a look - it's possible it's just some unexpected data internally causing it to fail.

Post Reply