bug(android): attempting to open a package from Files results in an error 'You don't have any apps that can open this type of file'

[mcdurdin]

Describe the bug

Reproduce the bug

No response

Expected behavior

No response

Related issues

No response

Keyman apps

• Keyman for Android
• Keyman for iPhone and iPad
• Keyman for Linux
• Keyman for macOS
• Keyman for Windows
• Keyman Developer
• KeymanWeb
• Other - give details at bottom of form

Keyman version

17.0.217-alpha-test-10103

Operating system

No response

Device

No response

Target application

No response

Browser

No response

Keyboard name

No response

Keyboard version

No response

Language name

No response

Additional context

No response

[darcywong00]

Previous issue #629 about Samsung's "My Files" browser.

As a workaround, does the Chrome Downloads allow you to install the .kmp file?

[mcdurdin]

Trying to install from Chrome Downloads, I get a toast from Keyman: "storage request permission was denied. May fail to install key..."

FWIW, any error which arises from a user action should be an alert rather than a toast.

[darcywong00]

Triaged with @mcdurdin to B17S1

[mcdurdin]

Trying to install from Chrome Downloads, I get a toast from Keyman: "storage request permission was denied. May fail to install key..."

Screencap. And a small insight into my life if you look carefully.

Screen_Recording_20240207_055457_Keyman.Alpha.mp4

[darcywong00]

MyFiles creates the intent that Android Studio warns with

[1235/FileExecute ] openFile() ] There is no activity that can handle the intent. (type : , data : content://media/external/file/11269)

Chrome Downloads does trigger the intent with

START u0 {act=android.intent.action.VIEW dat=content://com.android.chrome.DownloadFileProvider/... typ=application/octet-stream flg=0x10000003 cmp=android/com.android.internal.app.ResolverAct

[darcywong00]

Retesting with 17.0.289 beta and I see this in the Logcat trying to launch a .kmp file from Samsung MyFiles:

com.sec.android.app.myfiles          I  [1351/FileExecute         ] 
    getOpenFileIntent() ] unsupported file type extension : kmp, mimeType : 

I'll call this a dupe of #629 which has some unpleasant caveats with the intent-filters

Per SO reference, Samsung MyFiles browser

The sad answer is that is no good solution but to use */* and no file extension filtering.

When Samsung's file manager tries opening a file whose mime type they don't recognize, they default to passing "" (an empty string), which is impossible to filter for - setting an empty mime type in the intent filter creates a malformed APK that your device will refuse to install, so the only way to catch it is by using */*.

They probably should have defaulted to application/octet-stream, but that's not going to happen anytime soon - unless you work for Samsung, in which case, go change it :)

---

So, the only (uber unpleasant) alternative is to have an intent filter on all filetypes so the user could select Keyman for .kmp files.

Will close as won't fix - waiting on external

[darcywong00]

Re-opening to track for Future - still waiting on external Samsung update to MyFiles

[mcdurdin]

https://forum.developer.samsung.com/t/opening-files-with-unknown-content-type-from-my-files/30335

[mcdurdin]

Samsung have acknowledged that the issue is in their app but have declined to fix it. They don't consider Keyman a popular enough app to add specific support for it, and the hack that they've used for a long time is so embedded it can't really be fixed now, it seems.

I think we go ahead and close this as 'wont-fix' since it's outside our control and if necessary advise our users that they avoid the buggy My Files app, and instead browse for .kmp to install from within the Keyman app.

[mcdurdin]

Reopening and leaving forever in 'waiting-external' state because the issue is still present, even if we can't do anything about it.