Auto-upload to end-to-end encrypted folder not working
- Dominant language
- Kotlin
- Stars
- 5.6k
- Forks
- 2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 92
Description
### ⚠️ Before posting ⚠️
- [x] This is a **bug**, not a question or an enhancement.
- [x] I've [searched for similar issues](https://github.com/nextcloud/android/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](https://nextcloud.com/contribute/code-of-conduct/).
### Steps to reproduce
Go to Settings -> Auto-Upload -> (choose some folder) -> Configure -> (enable) -> Remote Folder.
Then Choose an end to end encrypted folder.
### Expected behaviour
The folder is choosable, or at least there is some information about what can be expected to work with end-to-end encryption.
### Actual behaviour
Toast message saying "Copy/move into encrypted folder currently not supported".
---
Scanning through older bug reports I get the impression that auto-upload to end-to-end encrypted folders used to work at some point. See [10583](https://github.com/nextcloud/android/issues/10583) for example.
Also the error message seems weird, as it is talking about "copy/move".
Looking through the code a bit I suspect that perhaps a folder chooser component was reused for choosing the target folder for auto-upload and that folder chooser component has different expectations about what it will be used for and how that interacts with end-to-end encryption, than what is currently true. Hence the weird error message. Only a guess though.
### Android version
10
### Device brand and model
Moto G7 power
### Stock or custom OS?
Stock
### Nextcloud android app version
3.31.0
### Nextcloud server version
30.0.6
### Using a reverse proxy?
I don't know
### Android logs
_No response_
### Server error logs
```bash
```
### Additional information
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.