We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
Conflicted copy on a folder?
OK, I understand the principle of what creates a conflicted copy with a file, which has been updated while another user (or the same user's account on another machine) has also updated it remotely. ...
We'll try that! FWIW, we've now seen the problem on a second machine (a macOS one), so this isn't down to an individual machine's configuration. OTOH, we've seen this work successfully on a bunch of other machines with no problems, so it's not univeral.
* universal
Sigh. Disregard last two comments; both failures were still on the same macOS machine. (There was a separate failure on the Windows machine, not a conflicted copy.)
- Hannah
Dropbox Community Moderator
Thanks for the additional info, Jon.
Once you have an update about the process suggested by Nancy above, let us know!
Updates at last! I can confirm that turning off syncing avoids the problem. And the problem is still only appearing on one macOS machine.
Here's the events log and a Version History for the (failed, deleted and now restored) "Level 2A - Encrypted" folder, from a new test run:
Briefly, it shows the "Level 2A - Encrypted" folder being re-added under that name (for no reason that I can detect), then deleted again, right before the encrypted folder is renamed back to "Level 2A - Encrypted"... and this still causes the folder to be renamed with "(conflicting copy)".
- Nancy
Thanks for the updates, Jon! Just one thing to clarify, does the issue persist on a specific device now, or pausing the Dropbox app’s sync has resolved it in general?
