Describe the bug
Say I'm opening a file in default browser from smb server folder. Normally opening a file with simple tap produces path like this 127.0.0.1:PORT/path, which works as expected. But if I open a file using "Open with" menu, it produces a path like this content://com.amaze...etc.../USERNAME:PASSWORD@IP/path , which leaks credentials to third party apps (eg: browser). As a result, file fails to open.
Describe the bug Say I'm opening a file in default browser from smb server folder. Normally opening a file with simple tap produces path like this
127.0.0.1:PORT/path
, which works as expected. But if I open a file using "Open with" menu, it produces a path like thiscontent://com.amaze...etc.../USERNAME:PASSWORD@IP/path
, which leaks credentials to third party apps (eg: browser). As a result, file fails to open.To Reproduce Steps to reproduce the behavior:
Smartphone: