Custom filenames end with year instead of the expected incremental number
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 13
Description
Using the following filename mask: YYY-MM-DD_HH-mm-ss_ in the iOS app, shows the right expected preview of the filename: 2020-04-10_23-22-10_0001.jpg.
However, after enabling the "Upload the whole camera roll", the generated filenames are all ending with the year value: 2018-02-09_20-42-50_2018.jpg
Nextcloud for iOS 2.25.9.2.
Nextcloud Server 18.0.3
Reinstalling the app, resetting application and clearing the cache doesn't help.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Reproduce the issue in the iOS app using the mask YYY-MM-DD_HH-mm-ss_ with whole-camera-roll upload enabled, then trace filename generation during that upload path. Done means generated filenames use the expected incremental suffix, such as 0001, instead of the year.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100