android
android copied to clipboard
nextcloud
Cannot get rid of file upload conflict notification
Steps to reproduce
- Get a notification like this
- Click it and end up at a dialog like this:
- 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:
?
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.
I finally managed to get rid of the incessant notifications but selecting both files.
File types are: pictures (JPG) and videos (MP4).
Yes, it’s a matter of auto-upload (camera-upload).
Von: Tobias Kaminsky [email protected] Gesendet: Donnerstag, 25. Februar 2021 08:50 An: nextcloud/android [email protected] Cc: Klemens2 [email protected]; Comment [email protected] 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 https://github.com/nextcloud/android/issues/7905#issuecomment-785694421 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKKGZZJ6WICG27VRQBIP25TTAX6JPANCNFSM4WXK33JA . https://github.com/notifications/beacon/AKKGZZN42PEI7U5JOTQSRT3TAX6JPA5CNFSM4WXK33JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOF3KL5VI.gif
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).
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 (https://github.com/nextcloud/android/issues/7082)
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 :/
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?
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 [email protected] Gesendet: Dienstag, 2. März 2021 10:15 An: nextcloud/android [email protected] Cc: Klemens2 [email protected]; Comment [email protected] 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 https://github.com/nextcloud/android/issues/7905#issuecomment-788752863 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKKGZZKY5WOYJCN3QFVQGGDTBSUAVANCNFSM4WXK33JA .
I also get this problem with random files with the camera auto-upload feature.
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 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 https://github.com/nextcloud/android/issues/7905#issuecomment-800016245 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKKGZZK2OYIZXMNX5C6PUZ3TD4AQTANCNFSM4WXK33JA . https://github.com/notifications/beacon/AKKGZZPAPE4C3CPK6Z6ZKS3TD4AQTA5CNFSM4WXK33JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOF6XUO5I.gif
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
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.
Same problem here. Even files, for which I resolved the conflict months ago reappeared today. Now I have hundreds of conflicts.
I'm also having the same issue. I currently have 124 of these conflicts asking whether or not it should keep the identical file.
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.
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.
Unfortunatly, the upload conflict notifications are back an my mobile. Around 10-20 each day. No entry (at all) in log.
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!
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
I have an issue that might be related to this one: https://github.com/nextcloud/android/issues/8653
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.
I am seeing the same issue on my phone as well. In my case though I have 19 conflicts that wont go away and are not displayed in the app. I have tried cleaning the NC apps cache but that did not help. This has been going on for sometime though multiple updates in my case.
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!
Thanks @jdaviescoates for the short-term workaround of selecting both file versions!
I still see this issue a lot, and am now wondering if my experience is being exacerbated by dueling auto upload rules. When I look under Settings > Auto upload, I have two separate occurrences of "Camera". One of them has a picture icon next to it, and the other one has a movie icon next to it, but when I ... > Configure each of them I see that they are both trying to upload /storage/emulated/0/DCIM/Camera to Remote folder /InstantUpload/Camera (all the other visible settings are likewise identical). I'm going to try disabling one of them and see if that reduces the number of conflicts while still successfully uploading both images and videos.
Are there supposed to be two auto upload rules for the same folder? Is the icon actually meaningful?
(update: it turns out that disabling the movie icon instance of "Camera" caused it to keep uploading pictures but stop uploading movies from that folder -- no help)
I give up using autoupload function. Annoying. Last weeks, I tried to use it for a third person. I installed it to upload just when the phone is connected to power supply, that it should upload old pictures and to rename the files if there is a sync error. In fact, it didn't do any of these. It uploaded without connection to power supply, uploaded old files and showed the sync conflict dialogues. Really annoying, that for me this problems still remain evident and even are getting more/worse.
#9036 contains a fix. So does #8923 with another concept for "keep server version".