Upload queue does not respect updated duplicate-handling settings.

> Yep, Same frustration here.
>
> What configuration do you use for the upload?
>
> I had "move to app folder" which is unfortunately a must in order to have some safety on which pictures are actually uploaded and "always ask on duplicates".
>
> That combination caused all the troubles described here. Pictures not uploaded, tons of pictures in the queue waiting for upload although they were not existing anymore in the original folder because they were moved already by the app to the app folder etc.
>
> Switching to "rename duplicates" made it worse an created hundreds of duplicates on the server but not stopping to try to upload again and again.
>
> Since I switched to "move to app folder" and "skip duplicates", all photos are uploaded and moved. So maybe this hints towards the cause of others can confirm this.
>
> Unfortunately it seems that one has to wipe the app in order to change these settings because those pictures in the queue seem to be handled according to whatever config you had before.
>
> Loosely related to this topic. Can you think of a situation where it makes sense for the upload to replace a >0 byte file with a 0 byte file?
>
> Imho in that situation the app should always ask, even if skip or replace is configured because almost always replacing a file with a 0 byte version is wrong.

_Originally posted by @svenb1234 in [#16550](https://github.com/nextcloud/android/issues/16550#issuecomment-5077364561)_

まず Android のアップロードキューを追跡し、すでにキューに入っている項目について重複処理の設定をどのように読み取っているかを確認します。キューに入った写真を使って、報告された設定変更を再現します。0 バイトの場合も含めます。完了の条件は、キューに入ったアップロードが現在の設定に従い、誤って再試行したりファイルを置き換えたりしないことです。

索引モデルが issue の本文から書いたものです。