nextcloud
Images aren't being uploaded and are potentially lost (FullSizeRender name conflict)
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Open NextCloud app
- Go to Settings > Advanced > Change filename mask
- Enable "Maintain original filename"
- On a different phone, take multiple photos
- Airdrop the new photos to the phone that contains the NextCloud app
- Wait for NextCloud auto upload to kick in
- Auto upload fails with "423: WebDAV Locked: Trying to access locked resource"
I believe this error occurs because multiple different photos are somehow named "FullSizeRender.jpg", which causes a conflict when uploading the photos. Photos can be lost because they aren't uploaded to NextCloud and might be manually removed from the photo gallery
Expected behaviourTell us what should happen
Somehow airdrop photos are labelled as "FullSizeRender.jpg". The expected behaviour should be that the new unique photos will either have it's original filename (IMG_0001.jpg), or in case of a name conflict, a new filename will be selected (IMG_0001_1.jpg).
Actual behaviour
Unique photos with the name "FullSizeRender" are not uploaded to the NextCloud server. This happens with any extension (.mov, .jpg, .heic, etc)
Logs
N/A
Reasoning or why should it be changed/implemented?
Because the user doesn't know which photos aren't uploaded, they might permanently delete a photo from their library, thinking that it was saved in their Nextcloud server.
Environment data
iOS version: e.g. iOS 18.1.1
Nextcloud iOS app version: 6.6.0.4
Server operating system: Ubuntu
Web server: Apache
Database: Postgres 14
PHP version: Not sure
Nextcloud version: 31.0.2
@marinofaggiana Thinking that my photos were successfully saved to my Nextcloud server, I've permanently lost around 300 photos because of this bug 😞 I'm not too sure if this is a new bug, or an existing one. If there's anything I can do to help, let me know 😊
@marinofaggiana Is there a way I could provide logs or more context to this issue? I just had 50 photos sent to me via AirDrop and none could be saved to my Nextcloud server because the file name was FullSizeRender.HEIC 😞
Same here I think it is an issue with CLAMAV or redis... Php 8.3 everything else latest version (mariadb apache)
Same here I think it is an issue with CLAMAV or redis... Php 8.3 everything else latest version (mariadb apache)
This is not an IOS Bug - its server sided!
Here's what fixed it for me: In my case, it turned out to be related to ClamAV and resource usage.
- Switched ClamAV to run in daemon mode, as the standard mode was consuming ~95% CPU. (Also adjust clam av configs and settings.)
- Increased available RAM and adjusted relevant PHP settings.
- Enabled file locking and performed a full file rescan. (with occ)
- reboot
After these changes, everything has been stable again.
Unfortunatelly doing the above did not solve my issues :(
@marinofaggiana any chance this can get fixed in the next couple of releases? My photos are being lost since any name conflict causes the auto upload to drop the file.
Hi @marinofaggiana This issue is still happening even with the newest ios app version. I can send the affected photos over for you to try to run it locally and replicate it. It's so bad now that my old images are getting deleted because my old photos are named "FullSizeRender.HEIC" and the new air dropped photos are also "FullSizeRender.HEIC". Any help would be appreciated 🙏