Basically the title.
I'm not an Android app developer so this is mostly my understanding so far and would appreciate if someone can help/correct me here:
I had assumed that the only way for an app to permanently have access to files/dirs not created by itself was to ask the user explicitly. The user could in such cases use GOS's storage scopes to grant AND revoke access. I had also assumed that access via system-file-picker was transient and would be tied to the lifetime of the app - ie. once the app is closed the permissions are gone and it must ask the user via system-file-picker to select files/dirs again.
However, in case of system-file-picker, I can see that the apps can ask the OS for takePersistableUriPermission for the content uri that was shared with them. It's my understanding that for such a grant OS doesn't flag anything to the user. Is this true because if so it's a bit surprising to me as it's silently happening without the user being involved.
That grant will persist across app-sessions and even reboots and the only reliable way to get rid of it would be to uninstall -> reinstall the app.
So for eg. if FB is given a content uri of a dir via system-file-picker, it can (via takePersistableUriPermission have permanent/future access to that dir (and thus any new/old files there) across app-sessions and even reboots and the only way to revoke it seems to be to uninstall -> reinstall the app?