Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
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 .
now you confused me, this post was originally about vercrypt container no longer syncing properly, per file encryption (with or without filename) is a different technology (encfs or similar)
anyway, I see two issues some thing changed on the way syncing is detected and executed, and dropbox not comunicating any changes.
the 2nd is much worse in my opinion. with an information at least I could prepare myself in advance for the impact of changes.
I reported the original problem to support via a ticket when we found the issue -- I just got an email yesterday that they have submitted it to an engineer and will let me know when they have something to report. So, I'm hoping it was unintentional, and that they can fix it in the next release.
Thank you for your persistence I also reported the issue twice without any success.
