Kanbaru 🌟 (one hikari of too many)
(replying to Kanbaru 🌟 (one hikari of too many))
by the way, the solution to the same problem on iOS is just:
"UIFileSharingEnabled": true,
it's existed for thirteen years, it doesn't require any code, and it supports normal fucking POSIX filesystem APIs
1 replies
Saagar Jha
(replying to Kanbaru 🌟 (one hikari of too many))
Kanbaru 🌟 (one hikari of too many)
(replying to Saagar Jha)
@saagar I have of course seen their latest piece of comedy
Saagar Jha
(replying to Kanbaru 🌟 (one hikari of too many))
Kanbaru 🌟 (one hikari of too many)
(replying to Kanbaru 🌟 (one hikari of too many))
this is made all the more confusing by the fact newer Android versions still use the “file” and “file manager” metaphor in user-facing text, and there is a long list of exceptions that make it very hard to make general statements. many users will not have noticed the change.
Kanbaru 🌟 (one hikari of too many)
(replying to Kanbaru 🌟 (one hikari of too many))
in Android 11, Google fundamentally changed what a file is and what a file manager does, without communicating this to users. we as app developers are left to pick up the pieces, desperately trying to explain this incomprehensible system to users who think we're gaslighting them.
1 replies
Michael Dwyer
(replying to Kanbaru 🌟 (one hikari of too many))
@hikari
Um ... I was honestly hoping you would follow this post up with that explanation.
Because all I know is that, if my web browser ever downloads a PDF file instead of opening it itself, then that PDF file is gone forever.
Future archaeologists will find my pile of lost files some day and wonder why the hell someone ever needed twelve copies of the same file.
I hate what Android has become. The "freedom" argument I used to make is ringing hollow now days.
Kanbaru 🌟 (one hikari of too many)
(replying to Michael Dwyer)
@mdwyer unfortunately it's so complicated that nobody who understands it understands it completely, nor do they want to explain it
Kanbaru 🌟 (one hikari of too many)
(replying to Kanbaru 🌟 (one hikari of too many))
btw while Google were reinventing the filesystem they created a new URI scheme for “content” that is apparently unusable for the most important application of URIs, namely hyperlinks. opening “content://org.touchhle.android.provider/” brings up… the Messages app??? what the fuck
Kanbaru 🌟 (one hikari of too many)
(replying to Kanbaru 🌟 (one hikari of too many))
ok never mind, it's just “content://org.touchhle.android.provider/root/root”. allegedly this only works on some devices but look, that's almost a normal URI. do not ask me why it opens Messages if i get the path wrong
Kanbaru 🌟 (one hikari of too many)
(replying to Kanbaru 🌟 (one hikari of too many))
btw adb shell am to-uri and adb shell am start-activity are extremely useful.
also in case you didn't believe me about the file manager not being a file manager: its true name is com.android.documentsui