Auto upload: unwanted duplicate
⚠️ Before posting ⚠️
- [X] This is a bug, not a question or an enhancement.
- [X] I've searched for similar issues and didn't find a duplicate.
- [X] I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
- [X] I agree to follow Nextcloud's Code of Conduct.
Steps to reproduce
- Configure Camera folder
LocalAto be auto uploaded with Year/Month structure toRemoteAfolder - Configure another, diffferent folder, e.g.
LocalB, to be uploaded into a different folder from Camera folderRemoteBalso withYEAR/MONTHstructure
Expected behaviour
Images from LocalA are uploaded to RemoteA/YEAR/MONTH
Images from LocalB are uploaded to RemoteB/YEAR/MONTH
Actual behaviour
Images from LocalA are uploaded to RemoteA/YEAR/MONTH
Images from LocalB are uploaded to RemoteB/YEAR/MONTH
AND
to RemoteA/YEAR/MONTH/RemoteB/
Android version
13
Device brand and model
Google Pixel 7 Pro
Stock or custom OS?
Custom (explain in "additional information")
Nextcloud android app version
3.25.0
Nextcloud server version
26.0.2
Using a reverse proxy?
No
Android logs
No response
Server error logs
There are none
Additional information
- Android Custom: GrapheneOS
- Why didn't upload logs: don't know how to run logcat on Android
Apparently, this issue doesn't appear consistently. In some cases, it is uploaded to the right folder. Which makes it even worse, because it happens unexpectedly
And I just experienced the case: after I moved an already uploaded picture on the nextcloud server to another folder (different storage), the nextcloud Android App uploaded the pictures again into the wrong folder (where the moved pictures had been uploaded before)
At least there seems to be a correlation: if there are pictures to be updated in the folder which is mentioned first in the auto-upload settings, the probability is higher for other pictures to end there as well (it is the wrong foldelr for them)
I see the same bug on a Samsung Galaxy S23 Ultra SM-S918B/DS with Samsung stock Android 13:
I have configured that /storage/emulated/0/DCIM/Camera is uploaded to /Photos/ using sub folders. A picture that is uploaded via AutoUpload is stored in /Photos/2023/07/ and /Photos/2023/07/Camera/
Nextcloud App has version 3.25.0. Nextcloud server runs Nextcloud Hub 3 (25.0.9).
Does someone know, if this bug will be fixed with priority or is the multi account functionality too rare as an uscase and resources are directed elsewhere. If so, I would consider a different backup system for my photos on my phone (google drive or similar). I realy love my Nextcloud system at work and my private one, however I can not use the autoupload anymore, it already pump GB of my private pictures to the company cloud where they are now stored in their back ups probably forever :/
There is no priority assigned, another issue most likely related didn't get attention after asking for priority yet: https://github.com/nextcloud/android/issues/11645 Probably there are too less devs or too many issues
Looks like this is the same problem that I experienced as well. See the screenshot:
You see that the same picture is uploaded to two different paths. I also had configured more than one local path. Then (while writing these lines) I realized that I had configured both /DCIM and /DCIM/Camera. After deactivating the rule for the DCIM folder it now seems to work.