Questions

I've been noticing a bug over the past few major releases that I've been able to work around but should be noted and hopefully fixed some how.

First, my setup:

2 computers, 1 android device

all 3 are setup to share via UrzaDirect

Computer 1 - mostly used for everything

Computer 2 - used less frequently to find stuff

Android - used the least often while away from home

The problem:

When UG is updated to a new major version, computer 1 updates the code, then updates my collection database, all is good.

Some random time later, UG runs on computer 2. Computer 2 has not seen the update yet, prompts to import the latest database from UrzaDirect, (click yes), then it fails. Red bar partially hidden below the bottom bar says something about database being from a newer version of UG and not imported. After manually going to the settings page, forcing the update, etc., the update works. The problem is in this time, the outdated version of UG which did not import the updated information from UrzaDirect has decided to write its outdated version of the database back to UrzaDirect. UrzaDirect database is now incorrect and missing all of the updates from Computer 1.

To get the proper database back, I then need to go back to computer 1, decline the request to import the latest from UrzaDirect, make some changes so the latest database is pushed back to UD, then go back to computer #2, resume whatever it was I was doing.

Repeat the process for the Android client as well.

If I had not noticed the error, obviously data would be lost from my collection. I do keep a local saved copy of the database file as well just in case I accidently click "yes" to the import losing my database on computer #1.

Is this something that can be fixed or am I using the UrzaDirect sync service incorrectly somehow?