-
|
I'm trying to rename a folder on my local repo, but I get this sync error:
I've checked and there is no remote folder with the new name. If it matters, the new name is the same of the old name, but lowercased. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
As far as Dropbox is concerned, the casing is cosmetic only and both paths are the same. That being said, such moves typically still complete successfully, even though the API docs claim:
I even have an integration test which ensures that it works and it has been passing without issues: Are you seeing the error for the parent folder itself or one of its children? And how many items does it contain? In the worst case, you might need to rename the folder on the Dropbox website instead. |
Beta Was this translation helpful? Give feedback.
-
|
I have worked arround it by renaming from XXX to xxx_a and then back to xxx |
Beta Was this translation helpful? Give feedback.
As far as Dropbox is concerned, the casing is cosmetic only and both paths are the same. That being said, such moves typically still complete successfully, even though the API docs claim:
I even have an integration test which ensures that it works and it has been passing without issues:
maestral/tests/linked/integration/test_sync.py
Line 216 in 2f82cdc
Are you seeing the error for the parent folder itself or one of its children? And how many items does it contain?
In the worst case, you might need to rename the folder on the Dropbox website instead.