We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Block-level sync for VeraCrypt not working post 83.4.152 update
Greetings all,
After DB auto-updated to 83.4.152, I noticed that the block-level syncing doesn't seem to be detecting changes anymore for my VeraCrypt container.
Before the update, everytime I di...
Hi all, we've brought this to our team and wanted to follow up.
While we've presented a workaround: either by turning off the "preserve file modification timestamps" setting in the application or naming the file with a ".tc" or ".hc" extension, we want to be transparent about our current priorities and unfortunately, this means that we won't be able to delve deeply into this in the near future.
We're still tracking these reports, and will make sure to inform you right away of any changes.
Thanks for understanding .
I'm seeing the same thing. It also stopped doing block-level syncs for TrueCrypt encrypted files (.tc extension). I've been using Dropbox for years with both TrueCrypt and VeraCrypt files and this new version 83.4.152 is the first update to break the detection of block-level changes when the encrypted volume is dismounted.
Please fix ASAP!!
PS: The only workaround I've found is to use: Copy filename.hc +,,
which forces a date modifed update on the file, but then Dropbox must upload the entire file (not just modified blocks) so it's terribly inefficient (not to mention inconvienient) . If they don't fix soon, I'll have to switch to a different cloud storage provider.
I have the same issue, but I think it started with version 82.
The ugly "workaround" I use, is to copy the "file" daily to "file_yyyymmdd", this syncs, and the immediately delete the file. While the orginal file is not synced, doing this I have a daily history, I can get if needed.
I think drobox either wants to save resources or has introduced a bug, it seems that a file is no longer checked on close alone, but only on close and the file date has changed. (I use the mode to not change the timestampo of the file)
- HI all,
Actual reason is Dropbox FS restrictions set: https://help.dropbox.com/installs-integrations/desktop/system-requirements#desktop Take a look especially on FS restrictions for different supported platforms.
Hope this casts some light.I do not think so, windows 10 with ntfs here, that should work or do I miss something?
And it used to work until 2019-10-04 (last sync in my history), so something else must have changed.Yes, my experience is the same with nei a., as I was able to utilize block-level sync functionality with VeraCrypt container (*.hc) and TrueCrypt (*.tc) before the 152 update. The last time that my container showed it was modified and synced before the manual workarounds (re-uploading the entire container) was October 13th.
In terms of next steps, what would you all advise? Is there an approach to submit this bug and escalate the issue to DB's support?
Thanks in advance, all.
