Local availability copying doesnt work on deeper nested folders (>2 subfolder levels)
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 13
Description
Steps to reproduce
- Have Nextcloud store some files in a deep directory structure, where the main folder F1 has a subfolder SF2 and within this there is another subfolder SF3 and again in SF3 there is a subfolder SF4 which contains a file, e.g. TEST.TXT
- Mark F1 as "offline available"
Expected behaviour
F1 and anything below it should get the green marker and all content should recurseively be downloaded locally
Actual behaviour
F1 gets the green marker (none of the stuff below it). Nothing gets actually downloaded.
Counterpoint:
This does work fine with up to 2 subfolder levels below the level where the users marks a node for local availability. So if the user in the above example marks SF2 for local download that does work.
I did notice this when I tried to make a cryptomator vault locally available. Cryptomator vaults have a lot of nested folders.
iOS version: 26.3.1
Nextcloud iOS app version: 33.0.3.7
Server operating system: Raspberry Pi OS Trixie
Web server: Apache
Database:
PHP version: 8.2
Nextcloud version: 32.0.6
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
Start by reproducing the issue in the Nextcloud iOS app with a folder containing more than two nested subfolder levels, using the reported versions where possible. Trace the local-availability recursion from marking F1 offline available; done means every descendant receives the green marker and is downloaded locally, while the existing behavior for shallower folders remains intact.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100