Cannot get rid of file upload conflict notification

[jdaviescoates]

Steps to reproduce

1. Get a notification like this

2. Click it and end up at a dialog like this:

3. Whatever I do (choose original file, choose the new file, or cancel) doesn't make any difference, within a minutes or so (or even less) I get the exact same notification about the exact same conflict again. Again, and again, and again

Expected behaviour

• Choose which file to keep, then not get the notification again.

Actual behaviour

• I keep getting the same notification about the same file conflict over and over and over again.

Environment data

Android version:

8.1.0

Device model:

Wileyfox Swift 2 Plus

Stock or customized system:

Stock

Nextcloud app version:

3.14.3

Nextcloud server version:

20.0.6

Reverse proxy:

?

[dremerb]

Can confirm this behavior. For me this happened after restoring a backup and re-syncing - I have set all folders to "Skip uploading" (not sure about the correct name, German system here) and the last conflict remains in the notifications.
Even after restarting the device, the sync starts again and the notification reappears.

[jdaviescoates]

I finally managed to get rid of the incessant notifications but selecting both files.

[Klemens2]

I have the same problem very often too.

[tobiasKaminsky]

What kind of file is this? Does it come via auto upload?

[Klemens2]

File types are: pictures (JPG) and videos (MP4). Yes, it’s a matter of auto-upload (camera-upload). Von: Tobias Kaminsky <notifications@github.com> Gesendet: Donnerstag, 25. Februar 2021 08:50 An: nextcloud/android <android@noreply.github.com> Cc: Klemens2 <klemens.heuboeck@gmx.at>; Comment <comment@noreply.github.com> Betreff: Re: [nextcloud/android] Cannot get rid of file upload conflict notification (#7905) What kind of file is this? Does it come via auto upload? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#7905 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKKGZZJ6WICG27VRQBIP25TTAX6JPANCNFSM4WXK33JA> . <https://github.com/notifications/beacon/AKKGZZN42PEI7U5JOTQSRT3TAX6JPA5CNFSM4WXK33JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOF3KL5VI.gif>

[dremerb]

When trying to get it working again, I encountered the following:
Deleted all of the existing files in Nextcloud. NC client on Android still had sync activated.
Uploaded images from Android to NC (auto upload does not do this automatically). Instant conflicts.

Also, often NC client on Android fails to build the conflict dialog (Message along those lines in a Toast).

[wknds]

I experience the same issue on an autoupload folder. I am working on Nextcloud android client 3.15.0
I thought this issue has been resolved in some older version of the client (#7082)

[tobiasKaminsky]

I use the app for auto upload also on daily base for my own purposes, but I never managed to create such a conflict problem when using auto upload.
Even when I create manually a conflict, I can see conflict dialog just fine.

Do you have reliable steps how to reproduce this? Also on other devices?
Otherwise I am currently out of clue how to debug this :/

[wknds]

In my case, i am syncing the folder Screenshots with Nextcloud. Let say the folder is synced. Now i am using a file browser and upload an already synced file to the folder Screenshot on Nextcloud. The issue from above appears. (Nextcloud android client 3.15.0). Can anybody confirm this?

[Klemens2]

The syncing problem appears on my phone (Fairphone 2, android 7) as well as on the mobile of my wife (Xperia Z3+, android 5), in both cases when auto-uploading photos with last android app and NC 20. Von: Tobias Kaminsky <notifications@github.com> Gesendet: Dienstag, 2. März 2021 10:15 An: nextcloud/android <android@noreply.github.com> Cc: Klemens2 <klemens.heuboeck@gmx.at>; Comment <comment@noreply.github.com> Betreff: Re: [nextcloud/android] Cannot get rid of file upload conflict notification (#7905) I use the app for auto upload also on daily base for my own purposes, but I never managed to create such a conflict problem when using auto upload. Even when I create manually a conflict, I can see conflict dialog just fine. Do you have reliable steps how to reproduce this? Also on other devices? Otherwise I am currently out of clue how to debug this :/ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#7905 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKKGZZKY5WOYJCN3QFVQGGDTBSUAVANCNFSM4WXK33JA> .

[danielb7390]

I also get this problem with random files with the camera auto-upload feature.

[tobiasKaminsky]

From other issues I read that the problem might be that very big files are not uploaded in time (assembly on server takes some time, but client does not wait that long and thus it is marked as failed), and then the same file is tried to be uploaded again.

--> Is this only happening on large files?

[Klemens2]

You might be right, because I remember, that often it have been video files, but I’m not sure, i fit were always big video files. I think, sometimes it has happened to pictures, too, but I‘ not sure. Von: Tobias Kaminsky ***@***.***> Gesendet: Dienstag, 16. März 2021 08:15 An: nextcloud/android ***@***.***> Cc: Klemens2 ***@***.***>; Comment ***@***.***> Betreff: Re: [nextcloud/android] Cannot get rid of file upload conflict notification (#7905) From other issues I read that the problem might be that very big files are not uploaded in time (assembly on server takes some time, but client does not wait that long and thus it is marked as failed), and then the same file is tried to be uploaded again.

…

--> Is this only happening on large files? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#7905 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKKGZZK2OYIZXMNX5C6PUZ3TD4AQTANCNFSM4WXK33JA> . <https://github.com/notifications/beacon/AKKGZZPAPE4C3CPK6Z6ZKS3TD4AQTA5CNFSM4WXK33JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOF6XUO5I.gif>

[danielb7390]

The last conflict i got yesterday it was a JPG file ~2MB

[jdaviescoates]

As per screenshots of my original post when this happened me the file was just 55kb. But eventually I checked both check boxes to keep both versions and it resolved itself (but there is actually only one version of the file on the server). It's not happened to be again since

[dremerb]

Finally had some time, tried to replicate.
Android Client Version: 3.15.0
Server Version: 19.0.1

What has broken for me in the past:
Had automatic backups running to replicate data from my phone to cloud. Broke Android one day (custom ROMs ftw -.-), downloaded all data from NC to desktop computer, loaded it to Android via USB.
Then I rebuild the automatic upload structure, so all files that were copied manually to the phone should once again be synced to NC - to the locations I've just downloaded it from. This produced said error. Automatic upload was set to skip uploading, if a conflict occured, but this was ignored.
Fix was (in this exact order!) to disable automatic upload, wipe data from cloud, re-setup automatic upload. There was no possible way to keep data in cloud and just setup NC on Android to use that folders again, always threw conflict messages.

What I've tried now: Created folder in webinterface, created new, empty local folder on Android.
Loaded files into local folder on Android: synced as expected
Loaded file to cloud via webinterface: showed in app on phone as expected.
Loaded file to local folder on phone and immediately uploaded same file via webinterface: conflict in webinterface
Loaded file to cloud via webinterface and immediately moved the exact same file to local folder on Android: conflict notification in app.
Loaded file to cloud via webinterface and immediately moved the exact same file to local folder on Android with automatic backup set to skip files on conflict: no notification, seems to work as expected.

Conclusion: Can not replicate, although had the error earlier :/ Did no updates to NC server nor app since first occurence of the issue. All seems to be working as expected from my testing.

[StephanRichter]

Same problem here. Even files, for which I resolved the conflict months ago reappeared today. Now I have hundreds of conflicts.

[7RST1]

I'm also having the same issue. I currently have 124 of these conflicts asking whether or not it should keep the identical file.

[jdaviescoates]

Just to say again, what resolved this for me was to check both check boxes to say I want to keep both versions of the file (although in the end I actually only ended up with one version of the file). It's not happened to me again since.

[Klemens2]

Today, this worked for me too.

In the logs, i saw this entry (propably there is a connection to the problem)

Error	no app in context	Sabre\DAV\Exception\BadRequest: Expected filesize of 10240000 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 9306112 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.

---

[Klemens2]

Unfortunatly, the upload conflict notifications are back an my mobile. Around 10-20 each day. No entry (at all) in log.

[github-actions]

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

[solarjoe]

I have an issue that might be related to this one: #8653

[Knusper]

I also run into this.. and the notifications won't stop. It's the same file both on my device and the cloud - I tried to upload the same file twice via the share dialog from a sound recording app.

Selecting both files (instead of cancel) disabled the dialogue.

[bnavigator]

@knuser, @djripcord I got the same for new files.

You can get rid of the repeated conflict messages by removing the failed upload task in the App: left menu "Uploads" and them remove the failed uploads. But what we actually want is a successful upload, eh?

Removing the 404 redirection as suggested in #10423 did fix it for me.

[Knusper]

OK - this fixed it for me.

[gjedeer]

Maybe the app could check if remote and local checksums match, before bothering user? More work for phone is better than more work for user.

I too get these notifications all the time and learned to live with them.

[joelbrock]

Same issue here.
Android 13
Nextcloud app 3.21.1
NextCloud Hub II 23.0.3

My twist is the conflicts seem to appear only for images that I've EDITED locally. Usually in Google Photos on the phone. These create upload conflicts which will return day after day.

[tinwasp]

After changing my phone to a Pixel 7 Pro (running GrapheneOS) I have suddenly been getting pounded with upload conflicts as well over the last few months. Never been a problem before in this way. What I noticed, though, is that the checksums of the uploaded files are all off. They open and look ok, the size is the same as well, but the checksum is consistently different, affecting all, i.e. thousands of files. Wonder if something gets messed up here in the upload process.

Edit: Nevermind. Upon further inspection I realized, the only difference between the two files is the missing GPS info, as detailed in #6248, which has a workaround (#6248 (comment)). After fixing that, everything syncs fine again. Please excuse the noise.

[dodancs]

Nextcloud app 3.26.0 RC1 (beta)
Nextcloud server 26.0.3
Android 13
Oneplus 8 Pro (Oxygen OS 13.1)

I have the same issue on Nextcloud v3.26.0 RC1, Android 13, after I make some new photos and Nextcloud decides to upload them, after a while I get the conflicting file notifications. This also happens for photos I took many months ago, and then the notifications stack up as I make more and more photos and then the Instant upload is very slow to add new photos, because there is a backlog of thousands of notifications in the app to resolve conflicts (which are the exact same files on phone vs. server).

[Dante1349]

also with this issue right now, if anyone could help i'd be glad

[noyez]

I have not seen this error for quite sometime, but the latest update to Android v3.26.0 today brought back this error. When i tap on the "File Upload conflict" notification, i get the "error creating conflict dialog".

[Dulanic]

It happens quite often after updates etc... I finally gave up on this app and switched to something else because it was always problems. Try a webdav app instead.

[luisfcorreia]

This also happened to me recently, got a huge number of notifications that I can't fix.

Nextcloud Android - 3.26.0
Oneplus 8T - Android 13
Server - 27.1.0

[UllisHellfireeXperiments]

Same issue here, coinciding with the update to Android App 3.26.0. As someone said above the conflict affects random pictures mostly taken months ago. The issue affects all users (various smartphone brands, various Android versions) who use the auto upload feature, mainly for pictures.

Server: Nextcloud 27.0, meanwhile updated to 27.1

[prechberger]

I also have the same problem, I disabled the auto upload function but the notification still appears. I also updated the Nextcloud server from 26 to 27.1, maybe there is a connection with the Nextcloud version and the logging?
I don't have this problem on the IOS system, only on the Android version of the Nextcloud client app.

[stratus-ss]

sadly this started to recur after going away for a while

[T-Mike]

I also have the same problem, I disabled the auto upload function but the notification still appears. I also updated the Nextcloud server from 26 to 27.1, maybe there is a connection with the Nextcloud version and the logging? I don't have this problem on the IOS system, only on the Android version of the Nextcloud client app.

Exactly the same thing happens to me, it is very annoying because I have to force quit the app to stop these notifications.

[Glasairmell]

I am getting the file the conflict error on my pixel 8pro. Smaller jpg files make it to the server with conflict, however larger RAW files do not. The server I want to use is located in Germany and is producing this issue. The one in Nederland is not and working perfectly. That tells me it is not my cell phone Nextcloud install.

One could say it is a server issue. I can only guess at that though. Perhaps packets are moving much slower on one then the other or some kind of timestamp issue.

Perhaps the problem is with server set up or speed.

Cheers!

[Glasairmell]

Well nix the separate server ideal. Now BOTH of my servers have the file conflict issue. At this point I can find no solution to resolve this. I do not want to go back to OneDrive to sync my photos.

[Fruchuxs]

Same Problem, no possibility to kill all messages or to stop the uploads. Without a fix, the app is useless - sorry.

[hfr-hfr]

...did you try the manual fix as described in #10423 or here or here? It seems to work for many.

[Apflkuacha]

I've got two phones here running on different NC accounts - both show hundreds of these conflicts where the server and phone files are equal and have to be clicked one by one..

please fix such (several year old) bugs before implementing new features - more people leave NC because of such annoyances than you get from new fancy (but not necessary) features

[svenb1234]

Maybe related: #11974

[MafiaInc]

I got the same notification which is bothering me since there days now.
In my case I tried to upload a file from my Android phone via Nextcloud app from F-droid in directory where I forgot its read only for Nextcloud. Later I uploaded this file from a different place in the same directory, because my Nextcloud instance is configures to automatically scan the tree for new files in the file system it appears to find this file and shows it in the interface. Since then I can get rid of this notification. This was a temporary file anyway. I will try to remove it hoping this will remove that notification.

[MafiaInc]

After I deleted the file from the read only directory. I am now flooded with notifications of type :
"You are not permitted to upload to this
folder".
Attaching screenshot:

[joshtrichards]

@MafiaInc Check your Uploads tab in the app for the problematic file. It sounds like it's still in the queue so the app keeps re-attempting. You can remove it from the queue there.