https://bugs.documentfoundation.org/show_bug.cgi?id=164082
--- Comment #5 from Michael Weghorn <[email protected]> --- (In reply to Michael Weghorn from comment #4) > However, even there, my expectation would be that the > storage permission shouldn't be needed *if* file managers properly pass the > file to the app (using a content:// URL, not a file:// URI). If the crash happens due to a file:// URI being passed without storage permission being granted, that's of course not the ideal response in any case. If that's the cause, potential solutions could be: 1) show a warning if file:// URI gets passed, but file cannot be opened 2) drop handling for file:// URIs altogether, show a warning that another app didn't pass proper URI In line with the security concept on modern Android versions, I'd tend to prefer 2). But it would be good to first know whether that's actually the underlying problem here and it works fine with another file manager or when opening a file from another app, like a messenger or email app. -- You are receiving this mail because: You are the assignee for the bug.
