Thank you for your response.
It is described in the Sync Issues part in the Help. I misread, it states it is not an issue with the database. Because it is an issue with the validation I assumed it was cause by the Verify option :).
While itās not an issue of the local databases, it might be an issue of the sync store. Verifying the sync store and cleaning it if necessary is therefore recommended.
1 Like
I stopped using a VPN and still get the missing manifest error. Under iOS15 the problem persists as well.
I assume, or hope, that the missing manifest thing does not have consequences to the content of files. I have not noticed something gone missing.
Just thought Iād share my experience with this, in case useful to anyone (even though I sync via Dropbox, not CloudKit).
Yesterday, I ran into these issues with one of the databases thatās in a particular encrypted Dropbox sync store. DTTG showed multiple .manifest missing errors for that database, and had not synced it and would not sync it (triangle alert symbol on cloud sync icon). This was my first indication of something wrong. Then I looked on Mac, and while all the data in the database appeared to be intact, the DT3 log showed something like āmissing or broken sync data structureā, for that database.
After initial panic, I found this thread, which helped me a lot ā particularly the suggestions from @rmschne about using the procedures in the Troubleshooting section of the DT manual, and from @cgrunenberg about cleaning the database. Following those steps eliminated the problems on both MacOS and iOS, and so far (one day), so good. So thanks to them and thanks to all on this thread, and thanks to the DT team for providing these forums!
Not suggesting that those steps will always help ā AFAICT from this thread, those steps do not appear to have helped in other situations ā and I suppose it could be entirely different for Dropbox vs. CloudKit syncing. Just sharing one data point where they helped without having to rebuild databases or reinstall software, in case that helps anyone else. Iām on iOS 14.8 and MacOS 11.6, FWIW.
1 Like
Just as it is with shipping cargo or passengers traveling, a manifest is a document recording info about such cargo. Our manifests are the same.
So, what can go wrong with this error message? Anything to watch put for?
So, what can go wrong with this error message?
The error message is not-fatal in that itās not causing damage to your files.
It means it canāt reconcile the data from the sync dataās transmission on one end with data at the destination on the other end.
This means the databases just wonāt sync properly so each device would have its copy of the database in a different state.
Getting the same error after the iOS 15 update- iād been running the betas with no great issues, with and without VPNs & Apple private really.
Seemingly soon after installing the iOS GM this week, my DT3 logs started filling with manifest errors- for one specific file in one database on the Mac (which is on Big Sur), and for multiple files across multiple databases on my iPad. I need to go through the manual as suggested above, but for now, my CloudKit data sync is stopped cold, which is vexing due to recent new file import. Just an FYI really, Iāll let you know if I can determine something more specific & hopefully useful.