DT3 Pro - sync Dropbox menu bar progress stuck

[mog]

Ever since I set up a sync, the dropbox menu bar progress has stuck, as per the attached screenshots.

I have reinstalled Dropbox but to no avail. The sync progress was working fine before I set up the DT3.

I have disabled the DT Packet Sync, could that be the reason?

Any suggestions?

[BLUEFROG]

That would be a question for the Dropbox support team.

And yes, you should disable the DEVONthink Packet Sync folder, per our instructions.

[rfog]

This happens to me so and then with dropbox and is not related to DT sync or indexed folders. It happens with very little frequency (two or three times since Dropbox enabled “on demand” sync) and ends having to restart my iMac. Seems it uses a hidden Safari instance to do something, or Safari engages by some manner with dropbox and my iMac ends not being able to kill drobpox and safari and needed a forced power off.

Once restarted all worked fine.

[scotte]

I’m trialing DT3 Pro on an iMac and Macbook Pro. I too find the sync (iCloud in my case) get frozen syncing, but when I check the other machine, it appears that everything has synced completely.

[BLUEFROG]

Wecome @scotte
See this…

iCloud upload….DT3

No worries at all, @Wolkenhauer and it’s useful in the sense it can underscore the situation with what DEVONthink’s sync with iCloud is doing. Many people mistook the finish of activity in DEVONthink’s Activity window / pane to mean data was on Apple’s servers and should be on their other devices shortly (which is actually how the Dropbox sync does work!) This is why we changed the messages in the Activity to… Preparing items for iCloud = syncing to the local machine set aside for us in iCl…

[scotte]

Thanks for the quick response - I’m not sure what the intent of the window is then showing that it is at 5 of 7 items and stays like that for a long time. I interpret that as it is stuck and the sync / copy action has not completed although it does actually look like the sync / copy action did complete.

Putting my developer hat on, it almost looks like the last update to show completion did not occur or didn’t get processed by the UI before the background worker shut down.

[BLUEFROG]

Development would have to assess and respond to that.

[cgrunenberg]

It’s a known issue that will be fixed by version 3.0.1