Edit: oh we already have them in the other submission
I know, I used to be one of those
Android old file API had blank access to ALL files on device. This was deprecated. New API requires individual permission for each folder. Or without permission, app can use file dialog provided by operating system.
Google apps have the some conditions. On many vendors they do not even have file permissions in default installation!
The "sync just one folder" functionality exists in SAF without any high-risk permissions. Migration of existing profiles may be a pain (as the user would need to grant permission on the folder when switching to the new API).
Synchronisation of the entire virtual storage, the download folder, or any extra folders vendors like Samsung might've added to the blacklist, isn't possible with the new API, but it's also not possible with Google's own services. The DMA only requires Google not to be put in a special position; as long as they don't offer such a feature, they don't need to offer it to NextCloud.
But yes this is shitty regarding google.
SAF can be used. There are reasons why this wouldn't be a good fit for NextCloud (you can't share your entire internal storage, your download folder, or the root of an SD card, for instance), but I don't think NextCloud's statement makes sense.
https://developer.android.com/training/data-storage/shared/d...
This was discussed yesterday:
Bottom line: Googles "least-privilege" rhetoric sounds noble, but in practice it gives Big Tech first-party apps privileged access while forcing independent vendors to ship half-working products - or get kicked out of the Play Store. The result is users lose features and choices, and small devs burn countless hours arguing with a copy-paste policy bot.
However, AFAIK, this problem would not apply to the NextCloud app.
jsnell•2h ago
sierra1011•2h ago