Repository navigation
Excessive file upload conflicts after update to 3.26.0 (not before) #11974
Description
Activity
Same here on three (Android) phones that just upgraded the client app.
Started receiving this behavior last night (I'm guessing am automated update). I suddenly began to get hundreds of upload conflicts from photos that were backed up months ago.
I can't dismiss notifications because as soon as I do, another 24 are generated.
Samsung galaxy s23 ultra
Client version: 3.26.0I think the app settings got messed up after the update. I had to change this setting
"What to do if the file already exists" back to skip uploading.It didn't seem to help.
I uninstalled and reinstalled the app. Then set up the auto upload settings again.
"What to do if file already exists? Skip uploading
"Uploading existing files" UncheckSo far it seems to be fixed.
Tried to take a look at the release to figure out what might have went wrong. Unfortunately the release notes appear to be poor/insufficient - even the ones on the app store is only a small fraction of what was put in the release
Looking through the closed milestone issues: https://github.com/nextcloud/android/milestone/84?closed=1
It seems there was some kind of change to auto upload to add support for other subfolder/dates or something. This seems to me to be the most likely to have cause an accidental regression in sync functionality. #11642 and #11852, tagging the author in case @dean36963 and approving reviewer @AndyScherzinger
Note: I am not a nextcloud developer, contributor, or even an android dev. Just trying to help move this issue along.
Reacted by istoppedcaringat30, StevieTV, RikkiBC, Markus Ritzmann, Heistergand, lftsy, Bene and Patrick MotardYep I'm stuck with this also, a few thousand files all from my instant upload folder became conflicted. Following this, if theres any info needed then happy to share
Seeing the issue here as well...my solution for now was to turn off notifications w/in NextCloud in the hopes that a future (soon) release will correct the behavior.
I'm getting multiple of these alerts too; but strangely all for one file uploaded over a week ago, one of a batch of 20 or so. All the alerts refer to this one file though. Odd.
If I click the alert, I get "Error creating conflict dialogue!" pop up over the files screen.
Same issue here, the Android App floods my push messages with file upload conflicts
Same issue here as well. This has happened before in the past. Unacceptable update, where are the Dev's with communication?
just confirming I've got the same error too:
nextcloud android app - 3.26.0
nextcloud server (via helm chart) - 27.0.2
reverse proxy - nginx ingress controller latestSame for me, some screenshots below.
All seem to be stuck between February(more than 1 day, I've seen 2 so far) 2023 and whatever the original date (to the right- server version) should be.
Same here. Downgraded to 3.25.0 for now.
Sorry if I'm being annoying, but with no developer acknowledgement that the current "stable" release is broken for a growing number of users, I'm tagging in the remaining approving reviewers of the likely problematic PR: @marcoambrosini @jancborchardt @tobiasKaminsky
The bug/regression of repeatedly finding upload conflicts is not only very frustrating, it seems nextcloud has bumped up to my top 3 battery draining apps, whereas before it was negligible.
Reacted by StevieTV, saruter, Aric Forrest, Andreas Scherbaum, Lennart C. Karssen, Alexander Müller, Markus Ritzmann and mark preston237 remaining items
- moved this from 🏗️ In progress to ☑️ Done in 🤖 🍏 Mobile clients team
on Feb 8, 2024 For checking if files are identical: have you considered comparing the file checksum? If I'm not mistaken that is stored and available as part of the file metadata on the server, right?
As mentioned and referenced we currently do not have checksums provided by the server. This has been discussed numerous times over the last years but always decided against impllemeting it due to expected issues in terms of server performance and database impact in terms up updating the db structures and also calculating the checksums for existing files which is expected to be a huge issue on very large instances with many files.
Implement it ad-hoc then? Nextcloud has left me with numerous files that got corrupted to 0 bits in recent times, I've always wondered why my phone kept corrupting files, thinking my phone's storage must be unreliable. But then I looked at some NC conflicts and I found it curious that there's an obvious connection.
A sync client that practically destroys files needs to at the very least emergency halt the feature altogether, I'd rather have no sync than corrupted files until the lucky day I happen to clue together what might be the problem. This inspires zero confidence in NC for what I consider to be one of the most core, basic needs one might have for an application like this.
I'm flabbergasted this is unhandled for months.
Reacted by Max Bordun, TCH, Pavel Peřina, Torbjørn Viem Ness, JulienFS and r-nd-m- Yes, they where identicalBest regards
For checking if files are identical: have you considered comparing the file checksum? If I'm not mistaken that is stored and available as part of the file metadata on the server, right?
As mentioned and referenced we currently do not have checksums provided by the server. This has been discussed numerous times over the last years but always decided against impllemeting it due to expected issues in terms of server performance and database impact in terms up updating the db structures and also calculating the checksums for existing files which is expected to be a huge issue on very large instances with many files.
I don't know if the team realizes or not, but this file corruption issue is poisoning the NextCloud name. Performance issues are tolerable; data loss is not. As soon as I encountered this myself - and at a surprising scale - I disabled the NextCloud container completely... I hope to see a robust solution posted in this thread someday so that I can give it another go.
If you're declining checksums, what's the alternative that's being worked on?
Reacted by Glassed Silver, Maximilian Ehlers, Mathis Brossier, djamn, Pavel Peřina, Torbjørn Viem Ness and r-nd-m- I did witj the linux shell
Please shift further file verification discussion to the issue that already exists for tracking it:
Reacted by RikkiBC, q-wertz and SiressPlease shift further file verification discussion to the issue that already exists for tracking it:
Issue is 8 years old, easy to see why people don't instinctively post there when the way HOW this is tackled is the least of user's concern.
But sure I'll add my feedback there as well, because whether it fixes this issue or not, it's a needed feature anyhow, at the very least as an option.
Reacted by h3ndrikThanks for fixing this issue 🥳
Only noticed yesterday that the issue was gone in 3.28.0Reacted by Jonas Mayer, Glassed Silver and Ryan C- unpinned this issue
on Mar 19, 2024 I'm still stuck with this issue: on various Android 14 phones and with various users, the file is uploaded correctly and timestamps match, but the client is not moving the file to the renamed year/month folder, it keeps them in the original folder and then comes with the upload file conflict. I verify this on my phone by using a WebDAV client to copy files and skip existing files, and then remove the files on my phone. I have reinstalled the client on my phone, verified correct permissions but the issue persists.
@voidzero Please create a dedicated issue and do not post on this thread. Numerous things have changed so this is not the appropriate place to post about your situation. Thanks!
- locked as resolved and limited conversation to collaborators
on Aug 4, 2024
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Steps to reproduce
Opening android gallery to view pictures triggers the alert.
Take a picture triggers the alert.
Opening nextcloud app triggers alert.
Expected behaviour
Nextcloud wouldn't try to upload existing files.
Actual behaviour
Nectcloud is trying to re-upload some if not all of the pictures on my phone. I'll get 25 alerts at a time.
The pictures exist in both phone and nextcloud already.
Android version
13
Device brand and model
Samsung Galaxy S23
Stock or custom OS?
Stock
Nextcloud android app version
3.26.0
Nextcloud server version
27.02
Using a reverse proxy?
Yes
Android logs
No response
Server error logs
No response
Additional information
No response