I was going to experiment with links to “reverse” Dropbox’s nonsense.
It’s actually Apple’s nonsense. They’re just smart enough to shut up and let their competitors take the flak.
OK, thanks for all your replies (I’m the OP). I’m waiting for 13.1 before I update, and it seems to be coming next week, so from what you’ve all said, I’ll just dive in and, if necessary, manually alter the location pointers. (I have my file-syncing split between Dropbox and Sync.) We shall see.
icloud is at:
~/Library/Mobile\ Documents
Just curious… what is “Sync”?
You’ve found the Dropbox instructions…at top you provided link to:
Those instructions, far as I can tell are correct and worked just fine for me when I upgraded.
A new possible discovery with iOS Dropbox is that to enable “offline” files to iOS Devices, one must have a paid account. I’m researching to confirm this. If anyone else knows, I guess post here. I don’t blame them if true, but a change new to me, if true.
Rms, Sync is a Dropbox-like service, and OK’d hereabouts as also safe for syncing Scriv projects. Here…
Glad to know your upgrade went smoothly. Fingers crossed for mine hopefully, as I say, this week.
I don’t use Scriv on iOS or ipadOS so can’t comment on the paid thing.
I’ve been using Sync for my active projects for years. When Dropbox was blocked by the GFWoC—I was still in China at the time—I moved to Cubby, which was excellent, but shut down over 10 years ago, so I moved to Sync. They say it is not recommended for use with Scrivener, but my collaborators and
I have had no problem apart from shutting down a bit too quickly before the user.lock file has been deleted from the server. It’s the last step in the synchronisation process, and is easy to recover from.
Mark
Are there more experiences concerning sync with the new Dropbox client by now? Is it safe to update or will it break Scrivener syncing?
If you mean the move of Dropbox files to ~/Library/CloudStorage, I’m not aware of anyone who’s seen that change take effect. I wonder why they’re doing it, but it may be intended (somehow) to solve the problems people have had with online-only “smart” sync.
Apple demands this change, but doesn’t communicate the reason (or I completely missed that).
Perhaps it will allow better, safer support for Dropbox, not immediately perhaps, but it sequesters the files in a special location. Apple is quite fond of sequesters and sandboxing.
Thanks for the link. That kind of makes sense. I don’t use OneDrive, so “Microsoft says that the new version of Files On-Demand can’t be disabled” sounds weird. Because in (the new) Dropbox version it is possible. Got the update recently and it works just fine.
The new file provider extension by Apple is simply awful: it is a memory hog that is constantly draining my MBP battery. My advice to others is don’t update, if you haven’t.
A strong recommendation. Using memory “memory hog” and consuming battery power should not really be directly related. Perhaps there is a troublesome file or folder? Any “sync issues” reported? Further, there might be a log somewhere?
Can you post your memory, CPU, and energy measurements to support your conclusions and recommendation?
Have you consulted Dropbox support on this and if so what did they say?
I must be blessed. See no issues like this. Now on macOS 13.1 and Dropbox v163.4.5456.
Hi, the new version of Dropbox for macOS brings significant changes - does it impact the use of Scrivener and especially the management of Scrivener projects already shared between device (macOS, iOS, Windows) ? Are there recommendations to implement before installing ths new Dropbox version ?
link to related Dropbox FAQ
You’ll find some existing discussion on this matter, above. The main thing to be aware of, to my knowledge, is this advisory, which has been in effect for a while now. By default it no longer syncs all of your data, which is bad for software that uses more than one file at a time to store archives of data.