No I am not running version 2.x. But having said that it might still be present on my time machine disk…Now that you mention it, I am trying to remember if it started unwillingly recently. It did happen in the past.
Try CloudMe - I switched when I had Dropbox issues and it has been rock solid since.
Except for this particular bug with DTPO, Dropbox has been rock solid for me and still is for everything else. I tried to move to iCloud before but that was problem.
So, signe all other applications (ans apps) seem happy, I am trying to find out what are the condition that make DTPO fail…
I hear you.
The problem is - you may not ever be able to know for sure you have identified the conditions when it fails. I tried. DT3 support tried to replicate it with my same data.
I suspect it’s a random issue with Dropbox, meaning there simply is no way you can ever be totally sure it works.
Note: You should not run DEVONthink 2 and 3 on the same account, on the same machine. At a minimum, you should delete DEVONthink 2.x from the /Applications folder and reboot the machine.
They should put in a redirect from http to https. Most companies do that.
Just chiming in that I seem to be having the same sync issues using dropbox as reported above.
Trying to sync multiple machines (5), after I do a “clean location” and all machines re-sync, by the end of a 24 hour period they are no longer syncing, but all machines report that they are. (I.e., in Preferences > Sync > Local, all machines report that they are sync’d at the most recent time, but they are, in fact, not.) No errors appear in the log.
As mentioned above, I can force the machines to sync by cleaning the database from the remote dropbox location. However, one of the databases is fairly large so this is a serious speedbump to any reasonable work flow.
As others have reported above, this issue is easily reproducible. Unfortunately, it reproduces itself continually.
Have not tried CloudMe but the prices make it an untenable option.
Any support would be appreciated before regretfully having to abandon the product. (I love DT when it works!)
As others have reported above, this issue is easily reproducible.
This is not the case. The issue isn’t reproducible at will.
Also, the recommendation in this instance is to create a new sync location with a new name and try syncing to it, not just cleaning the location.
Did you at any time on one of the machine start by mistake a previous version of DevonThink (from a TimeMachine drive or two instances of different versions of DevonThink install on one of the machine that could have run at some point between the first successful sync and the time this chain is broken?
I do not agree. There is something going on in the sync mechanism that lead to these broken sync (the scientist in me here speaking)…
Without being able to reproduce this and nothing useful in the logs so far it’s unfortunately hard to tell whether it’s an issue of Dropbox’ servers, the Dropbox SDK, DEVONthink’s sync or something completely different.
To clarify, by previous version do you mean DevonThink 2.5, or a previous version of DevonThink 3 – i.e. 3.0.3 rather than 3.0.4?
Now that you mention it, it is possible that one of the machines has/had not been updated to 3.0.4 when we last had the problem rear up.
Could that be sufficient to cause the sync misalignment?
Thanks for clarifying. I haven’t tried creating an entirely new sync location, with a new name. But I’m afraid with these machines being physically distant from one another co-ordinating to do this will be a substantial time suck. Here’s hoping I can fix it without resorting to that.
Appreciate the thought,
Matt
I was thinking a version 2 vs a version 3.
Been there done that. Splashtop or a similar remote access program can be a big help here.
That said, I tried setting up a new Sync Store in Dropbox and found it worked inconsistently and then the same problem recurred. Then it started working. Then it stopped. It happens often enough to make it unreliable for me but not often enough to make it reproducible. But it works fine for most people. Thus it is maddening to solve.
But it works fine for most people. Thus it is maddening to solve.
Absolutely true.
It’s like a hunt for Bigfoot. Not everyone has seen or heard it, but there are people that swear they have. And each time we go out looking, we have yet to see anything ourselves.