Description
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