Repository navigation
Auto-upload conflicts, yet again -- this is a never ending problem #16818
Description
⚠️ 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
- Configure your device's photo storage for auto-upload
- Take some photos
- Get a notification about conflicts
- Click notification to see conflicts
- Click one that says "Sync conflict, please resolve manually"
- Wait a few seconds
Expected behaviour
File should be uploaded to the server.
Actual behaviour
Toast message saying:
File not found. Are you sure that this file exists or has a previous conflict not been resolved?
Android version
16
Device brand and model
Pixel 8 Pro
Stock or custom OS?
Stock
Nextcloud android app version
33.0.1
Nextcloud server version
31.0.9
Using a reverse proxy?
No
Android logs
No response
Server error logs
NothingAdditional information
I'm not even sure why the Android app is saying there is a conflict as I have checked the server and the file reporting the conflict does NOT even exist on the server.
The Android device in question is not kitted to get debug info. It is a "production" device for a user and Developer options is not an appropriate security model for this device.
Ultimately this seems to be just yet another (of the many) bug(s) with auto-upload. I wish this feature could just work without constantly being a bug-ridden steaming pile.
Activity
alperozturk96 commentedon Apr 9, 2026
@brianjmurrell Hey
Thank you for the report. I created a PR for this once the APK is generated could you please try and share your feedback?
PR: #16819
brianjmurrell commentedon Apr 9, 2026
@alperozturk96 So, I installed the APK but it's a fresh copy of Nextcloud Android that has none of the customized (auto-upload and otherwise) config that my Nextcloud Android app has, so it will not see the same (buggy) behaviour and reproduce the same bug (to verify that it's fixed) as the proper Nextcloud Android app.
Unless I am misunderstanding what you are asking me to do.
brianjmurrell commentedon Apr 9, 2026
So, diving into this a bit deeper, I configured an auto-upload for the folder that has the files that are getting the sync conflict on Nextcloud Android (proper) but since I do not want to spend hours re-uploading thousands of photos in the QA app installation I did not enable Also upload existing files (since it's my understanding that that that option is not actually intelligent enough to not upload what is already on the server and just uploads everything in the local device folder, even overwriting the same existing file on the server if they are there already -- and I simply DO NOT want in any way to do that).
So TL;DR: I'm not sure how I am supposed to utilize this QA build to test this bug fix. I need an official Nextcloud Android build that will use the same database as my existing (non-QA) build to be able to see if this fixes the bug. AFAICT. Please correct me if I am wrong.
joe-average-user commentedon Apr 12, 2026
I have exactly the same problem. Auto-Upload worked until about 4 days ago. Then there was a (F-Droid) update to 33.0.1 and now it does not do any uploads at all but tells me for every file to solve a conflict which does not exist. I am on a Fairphone 5 with latest e/os. So drop the idea that this is android version specific. This code is obviously not even capable of understanding where a file is not present. It is present on the mobile, it is not present on the server. So it tells me it can't sync because it is not present? WTF ...
Ah, and btw the app version 33.1.0RC1 is broken, too. Exactly the same problem.
alperozturk96 commentedon Apr 13, 2026
@joe-average-user Hello
I created a PR for this once the APK is generated could you please try and share your feedback?
PR: #16819
joe-average-user commentedon Apr 13, 2026
@alperozturk96 Thank you for the PR, but I cannot check it, I only can replace the running app, but not add another one doing the same job. Anyway, since I am not able to give you a review this should be no problem for you and the code.
Your analysis of the problem looks correct to me, though. The current app behaviour does indeed not reflect the actual situation between android client and server. I did not expect that there is really no code in the current app that checks this... ?!?
ShaunMundy commentedon Apr 16, 2026
My last successful (auto-)upload was on 08.04.2026 since then the feature does not work anymore. [again]
On my tablet (Samsung Galaxy Tab 9+ | Android 16 | nextcloud client 33.1.0 RC2). The worst thing is, that after reinstalling the app, now even manual uploads don't work anymore!!
On my smartphone (Samsung Galaxy A22 | Android 13 | nextcloud client 33.1.0 RC2) It's exactly the same thing.
joe-average-user commentedon Apr 16, 2026
Just updated to 33.1.0RC2 and found out it immediately crashes whitel taping on a failed upload... Things can always get worse
3 remaining items
joe-average-user commentedon Apr 19, 2026
Ok, I just got RC3 and have to say that for the first time I saw a message that some conflict was resolved (automagically). And it did not crash any more. So it seems quite ok for now. Lets see how things evolve ...
joe-average-user commentedon Apr 19, 2026
Hm, something seem strange. I just took a photo with standard camera. Just as I thought it does not upload I found that it already was uploaded and the "Upload" windows shows it in a queue I never saw before named "Übersprungen" (Jumped over). I would expect to see it in "Fertiggestellt" (completed)-
alperozturk96 commentedon Apr 20, 2026
Hey thanks for the feedback. Could you please create another issue thus we can track the issues individually? Also please explain in detail what is expected behaviour and what is actual behaviour and how to reproduce.
joe-average-user commentedon Jun 12, 2026
Ah, the problem is not yet solved!
I just found out that a conflict is shown when the folder on the cloud does not exist. If you use dynamic subfolder year/month and the month has not been created yet you get a conflict because the check on the cloud comes back with "file does not exist"....
Please can you solve this one, too?
brianjmurrell commentedon Jun 12, 2026
@joe-average-user That is not the only problem. See that I have opened a new issue about a new conflict failure issue that has arisen since this PR landed. That new issue has gotten zero attention however so I don't hold a lot of hope out for your new finding here either.
This auto-upload and conflict resolution seems to be a pretty low priority for this project unfortunately given how many issues is has had in the past that have gone unfixed and how many it continues to have that go unfixed.
joe-average-user commentedon Jun 12, 2026
Really, I was very respectful for the work @alperozturk96 did last time, it really worked out. And the current problem with folders that do not get autogenerated seems minor compared to the mess we had before. Maybe we can revive his interest?
brianjmurrell commentedon Jun 12, 2026
I was too. Unfortunately it seems to have introduced more/different failures that seem fatal. There is simply no way to resolve the conflicts I have persistently in my auto-upload log. I click them, it says they are resolved and they remain there. Are they actually resolved? Who knows.
But it's yet another failure vector in what seems a long list.
alperozturk96 commentedon Jul 14, 2026
@brianjmurrell Hello
Could you please try with the latest generated QA APK and share your feedback?
Link: #17245
brianjmurrell commentedon Jul 14, 2026
I appreciate you having something to test, but as I've mentioned previously, that concept doesn't work because the QA APK does not share the same state as the production one so (a) I don't have the same list of upload folders and (b) it does not show the same list of conflicts so I cannot test whether those conflicts that won't go away in the production installation will actually go away if I click them to resolve them in the QA builds.
burner- commentedon Aug 25, 2026
I tired to this bug. Looks that client did not do any kind hash check. Instead it just check date, name and size. However resolve this with AI by doing hash check. Aftet that I stop getting false positive conflicts. Here is patch 03ad3ed
However it is 100% vibe coded and I am not sure of its quality so I did not do PR of it. But as reference I must say that it was big surrprise for me that client wont event try make any kind checksum check at conflict situation. And it explain why I some times get thousands of false positive conflicts.
alperozturk96 commentedon Sep 14, 2026
Hey,
Could you please try to reproduce the issue described in the first message using 35.0.0 RC2 and let us know whether the issue has been resolved?
To help us keep things organized and make sure we can track each issue properly, please keep this discussion focused on the issue described in the original report.
If you notice a different issue, have a separate feature request, or would like to discuss another improvement, please create a separate issue for it. This will help us investigate and track each topic individually.
Thank you for your help and feedback! 🙌
brianjmurrell commentedon Sep 14, 2026
How would I go about doing that? I would need a binary that updates my existing Nextcloud client install since the unresolvable conflicts are in it's database. Debug installs of the app cannot be used to test as they don't share the database and therefore would not see the existing unresolvable conflicts with which to test against.
brianjmurrell commentedon Sep 23, 2026
Issue still exists with 35.0.0.
I still have 7 (getting) old conflicts that when I click them they show a toast notification Conflict resolved. but the conflict does not get removed from the conflict list.