Syncing With a PartnerĪll that said, we know there is a particular use case with Dropbox sync that is really important to a lot of people-the ability to sync with a spouse or partner. Finally, iCloud sync is a lot less difficult for people to enable, as almost everyone with an iPhone already has an iCloud account.įor all of those reasons, we decided against re-implementing Dropbox Sync.
It’s more difficult to troubleshoot when we have to contend with two sync systems, or figure out which sync method someone is trying to use, or figure out what sort of problem could occur when people have both sync methods enabled. Pus, supporting two sync methods has always been troublesome. In addition, all the time we spend on re-implementing sync is time we can’t spend developing new features, fixing bugs, or refining Chronicle in other ways. We looked into the new Dropbox API, but realized quickly it was going to be a lot of work to re-implement the sync well. It’s also automatic, while Dropbox sync we implemented as a manual process. Since the switch to CloudKit, Chronicle sync via iCloud has been much more accurate and reliable. This would mean we would need to completely re-write the Dropbox sync code in order to keep Dropbox working. We had recently just went through a similar procedure re-writing all of iCloud sync to support CloudKit, Apple’s newest sync framework. Last year, Dropbox announced it was ceasing to support the Dropbox API that Chronicle and many other apps used to sync with Dropbox, in favor of a new API. If it’s not done correctly, it could lead to lost data or other problems.
Syncing is the most time-consuming, difficult thing to implement.
The short reason why is that Dropbox disabled the API that Chronicle uses to communicate with the Dropbox servers. More details are below: Why We Dropped Dropbox Sync On older versions, the sync will stop working on September 28. Here’s why: The latest versions of Chronicle for Mac (8.0) and iOS (7.1) removed the option for Dropbox sync.
0 kommentar(er)
