Auto upload conflict detection not working correctly

[dataprolet]

⚠️ Before posting ⚠️

• This is a bug, not a question or an enhancement.
• I've searched for similar issues and didn't find a duplicate.
• I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
• I agree to follow Nextcloud's Code of Conduct.

Steps to reproduce

1. Enable auto upload on any folder
2. Set to "Skip uploading" if file exists
3. Get notification "Upload failed Conflict" even though the file does not exist

Or

2. Set to "Rename new version" if file exists
3. File gets renamed indefinitely ("$file", "$file (2)", "$file (2) (2)", ...)

Expected behaviour

The app should either detect that the file does not exist and upload it or detect that the file already exists and do nothing if set to "Skip uploading". If set to "Rename new version" it shoul detect, that the file already exists and rename it once, then stop.

Actual behaviour

The app doesn't seem to correctly detect if a file conflict occurs. If the file does not exist it still detects a non-existing conflict.

Android version

16

Device brand and model

Google Pixel 7a

Stock or custom OS?

Custom (explain in "additional information")

Nextcloud android app version

3.34.1

Nextcloud server version

31.0.10

Using a reverse proxy?

Yes

Android logs

Nextcloud log afc001edf3d7.txt

Server error logs

Additional information

Using GrapheneOS Build 2025112101.

[joaociocca]

Same here, running on a POCO C75 with Android 15\Xiaomi HyperOS 2.0.201.0 and Nextcloud on docker (Nextcloud Hub 25 Autumn (32.0.2)).

I tried grepping for one of the files giving this error on the log:

2025-12-05 13:28:55  sudo grep 'IMG_20251204_191549.jpg' nextcloud-docker/data/nextcloud.log
{"reqId":"7tldK6QvIUjPOp5VKBUo","level":2,"time":"2025-12-05T03:45:12+00:00","remoteAddr":"","user":"--","app":"PHP","method":"","url":"--","message":"exif_imagetype(/var/www/html/data/johnny/files/Photos/2025/12/IMG_20251204_191549.jpg): Failed to open stream: No such file or directory at /var/www/html/custom_apps/recognize/lib/Classifiers/Classifier.php#301","userAgent":"--","version":"32.0.2.2","data":{"app":"PHP"}}
{"reqId":"7tldK6QvIUjPOp5VKBUo","level":2,"time":"2025-12-05T03:45:12+00:00","remoteAddr":"","user":"--","app":"PHP","method":"","url":"--","message":"filesize(): stat failed for /var/www/html/data/johnny/files/Photos/2025/12/IMG_20251204_191549.jpg at /var/www/html/custom_apps/recognize/lib/Classifiers/Classifier.php#106","userAgent":"--","version":"32.0.2.2","data":{"app":"PHP"}}
{"reqId":"2l5CGb2nmiLWvXvIRz6X","level":3,"time":"2025-12-05T04:00:07+00:00","remoteAddr":"","user":"--","app":"memories","method":"","url":"--","message":"Failed to index file /johnny/files/Photos/2025/12/IMG_20251204_191549.jpg: File is not readable: /var/www/html/data/johnny/files/Photos/2025/12/IMG_20251204_191549.jpg","userAgent":"--","version":"32.0.2.2","data":{"app":"memories"}}

Let me know if there's anything more of use on the log to grep, mine's currently too big to share here =(

[alperozturk96]

Hello

@joaociocca @dataprolet

Auto-Upload logic completely redesigned. Could you please try with 3.35.0 RC2 and share your feedback with us?

[dataprolet]

The v3.35.0 RC2 ist really buggy. I configured Auto upload on several folders and it uploaded all files in separate folders. But in the upload section of the app the files appear as "A file with the same name already exists", even though they were uploaded.
Also at some point when clicking the hamburger menu or the lower buttons ("All files", etc.) it was not doing anything. Instead an "Assistant" button appeared and disappeared in the lower section.

EDIT: I'm also getting a "Folder error" on my custom folder, while the notification says "File not found", even though the file is present.

EDIT 2: Now I get the same Conflict error on a newly taken picture. So we're back to square one..

[dataprolet]

I've disabled all Auto uploads, but the app is still trying to upload files producing the above mentioned errors.

[dataprolet]

I've installed RC3 and it's still a hot mess. After enabling Auto upload and changing the upload folder and behavior it started uploading to the default folder using the default setting.
Whatever you did, Auto upload is basically completely broken and unusable.

[alperozturk96]

@dataprolet

Hello

Thank you for taking the time to test the new RC version. I’ve shared the issues with Auto Upload in this thread(#15214 (comment)) and we have addressed them. If you are still experiencing problems, we will work to resolve them as well, but I kindly ask that the conversation remain friendly and constructive.

I have configured the folder for Auto Upload and changed the settings, and under the same conditions, uploads are going to the correct location.

To reproduce the issue, I need the following details from you:

1. What is your auto upload configuration?
   Only upload on un-metered wi-fi on or off?
   Only upload when charging on or off?
   Also upload existing file on or off?
   Use sub-folders on or off?
   Exclude hidden on or off?
   Original file will be...? Kept in original folder, moved to app folder, deleted
   What to do if file already exists? Ask me everytime (which means create a notification for each file conflict), overwrite remote version, rename new version, skip uploading

2. What is the Android version and phone model?

3. Which storage permission do you have? All files access or media files or limited media files?

4. Was it custom folder, or you directly press the cloud button for specific folder from overview page (Settings → Auto upload)?

And lastly from Settings → Logs → via "auto upload" or "upload" keyword filter logs and share with us the logs.

Looking forward to your reply

[istvandbsd]

+1, I'm also seeing this on Android. Files get renamed indefinitely, and the queue size shown in the notification never seems to decrease, rather it seems as if starts over frequently.

My config:

Android version

15

Device brand and model

Sony Xperia 10 V

Stock or custom OS?

Stock

Nextcloud android app version

3.34.1

Nextcloud server version

32.0.1

Using a reverse proxy?

Yes

Auto-upload configuration

Only upload on un-metered wi-fi: On
Only upload when charging: Off
Also upload existing file: On
Use sub-folders: Off
Exclude hidden: N/A
Original file will be: Kept in original folder
What to do if file already exists? Rename new version

[dataprolet]

I updated to v3.35.0 and this issue persists. I can't express how disappointed I am in this app. It's been multiple RCs and now even a "stable" release and this issue hasn't been addresses.
Here's a recent log:
Nextcloud log | upload 0ae1b5ba6a3f.txt
Also CC at #16333 and #16332.

1. My settings are the following:
   Only upload on unmetered Wi-Fi? Yes
   Only upload when charging? No
   Also upload existing files? No
   Use subfolders? Yes
   Original file will be... kept in original folder
   What to do if file already exists? Skip uploading
2. Android version is 16 (GrapheneOS build 2026011301) on Pixel 7a.
3. Full media access.
4. I used the present media folders fo auto upload as well as added a custom folder.

[dataprolet]

Version 3.35.2 still hasn't solved this!
I observed that the original "Auto-Upload" folder was causing issues, so I created a new folder called "Autoupload".

• The app is still trying to upload to "Auto-Upload" even though the folder doesn't exist anymore. The folder is disabled, but present in the Auto-Upload settings.
• It then produces the same "Conflict" errors on the "Auto-Upload" folder which doesn't make any sense.
• When I remove the failed uploads from the "Failed/pending restart" section the uploads always reappear.
• Eventually the "Auto-Upload" folder got recreated and some files were uploaded.
• I assume the "Auto-Uploads" folder is stuck in a loop of failed uploads.
  Neither are my files uploaded into the correct folder, nor is the app respecting my actual settings but seemingly doing what it wants. This is especially unacceptable, because now I can't even trust to reproduce anything because the settings are apparently meaningless. I also don't want to reinstall the app again, because I rely on my calendar and other important thing being synced.
  For good measure here's another log: Nextcloud log 594c0ef50cec.txt
  I don't understand how a company this size is unable to release a working app and I'm actively looking for alternatives at this point.

EDIT: As a sort of workaround I edited the hidden folders in the Auto upload settings, set the folder from "Auto-Upload" to "Autoupload" and disabled them again. That seems to be working for now.
EDIT 2: That did in fact not work. Any upload is triggering the same files to try to upload to "Auto-Upload" and fail.

[dataprolet]

I have just updated to v33.0.1 and the following issues still persist:

• The app is trying to upload hundreds of old files to "Auto-Upload" even though I have no folder configured, that is uploading to that folder. I had this folder configured to auto upload previously.

• The app is in fact also uploading newly created files to "Auto-Upload" even though I have configured a folder to upload to "Autoupload". I had the folder "Auto-Upload" configured to auto upload previously.
  -> That results in many files being uploaded twice!
  -> I suspect (as of my previous comment) that the app is still using an old configuration of the folder "Auto--Upload" even though I have changed it already. This makes the app unusable, because user settings are disregarded by the app.

• The auto upload of many files fails, because the app is "Awaiting charge" even though I disabled "Only upload when charging".

• I am still getting "Upload failed Conflict" errors!!

• That results in many files being simply stuck at "Waiting to upload..".

I will reset the whole app and delete all settings in hopes that a fresh configuration will work.
I am still extremely annoyed and disappointed that this basic feature is still not working after over 3 month, since v3.34.1 and 5 app updates.

[alperozturk96]

Could you please follow the pinned issue and share the logs as described there?