File duplication error

[Siggi0904]

With 3.11 RC1 I get a file dupliccation error.

Files they are at NC won't be overwritten with newly update since 3.11 RC1.
I have to delete same named old files in NC before auto upload can upload these files.
Version's before aren't affected.

In my case I'll upload WhatsApp Backups to my NC storage.

Thanks for fixing or rolling back.

[AndyScherzinger]

Looping in @tobiasKaminsky and @ArisuOngaku - my guess is this is related to the upload existing files change (while it is just a guess)

[Siggi0904]

Hi, bug still exists with 3.11.0 RC2

[AndyScherzinger]

cc @tobiasKaminsky @ArisuOngaku this has been reported on the forum too
https://help.nextcloud.com/t/android-sync-file-conflict-setting-wont-work/73452/2

[ashpieboop]

Yes this is because there is no setting to let the user choose what to do in case of conflict. So we chose to let the user decide instead of doing a destructive operation by default.

We should add such a setting; What to do if the file already exists?:

• Ask me everytime
• Rename new version
• Overwrite remote version
• Ignore (are there use cases which make this preferable to "Ask me everytime"?)

[tobiasKaminsky]

Hm. Auto upload should only upload new files (after initial set-up).
So the conflict should only be there once.

@ArisuOngaku we should discuss this idea in a new issue 👍

[AndyScherzinger]

@tobiasKaminsky custom folder upload changes also!

[tobiasKaminsky]

I fear that there is no short term solution for this, but we should do this like Arisu said, and have an option how to deal with conflicts per each auto upload.

We should add such a setting; What to do if the file already exists?:

* Ask me everytime

* Rename new version

* Overwrite remote version

* Ignore (are there use cases which make this preferable to "Ask me everytime"?)

I would not offer ignore, as this might cause "data loss" due to not handling a conflict problem.

[tobiasKaminsky]

@ArisuOngaku do you have time to look into this? ❤️

[ashpieboop]

@tobiasKaminsky as I understand it, a file changing its content (at least in this specific case) gets handled like a newly created file (like if it was deleted then created again?). So in this case it would happen more than once.

Do you want this setting for 3.11.0?