Client is unaware of File Access Control restrictions, and how to handle them
- 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
1. Block some kind of file through the File Access Control app
2. Keep a folder synced that contains this kind of file
3. Check notifications after a while
4. You'll get endless notifications of "Upload Failed"

### Expected behaviour
This is bad/lazy behavior. The app should NOT continuously warn the user about an admin restriction.
* The user may not be able to do anything about it;
* The user may be needing to sync that folder anyway;
* The blocked file may be crucial and impossible to delete;
The app should discreetly warn the user about this, either with a single notification once, or in the Uploads folder.
Or better yet, **not warn the user altogether**.
It's an admin restriction, the user can't do anything about it - or the user is admin, in which case, he knows about it already.
### Actual behaviour
Having a file restriction becomes a severe annoyance for the innocent user.
Truth be told, the feeling here is that **the Sync app is not even aware** that such a thing as File Access Control exists.
A [seemingly identical issue](https://github.com/nextcloud/desktop/issues/5431) exists with the Desktop client.
Although, at least, the Desktop client can be told to _ignore_ the file.
### Android version
10
### Device brand and model
Ulefone 9
### Stock or custom OS?
Stock
### Nextcloud android app version
3.23.1
### Nextcloud server version
25.0.3
### Using a reverse proxy?
No
### Android logs
No Android app logs are available at the location indicated.
### Server error logs
```bash
No relevant Server error logs.
```
### Additional information
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.