Android: No app set up to handle this file type

[cieska]

Actual behaviour

Android NX app has a lack of option when opening an unknown file type. After error message user left without the option to choose from the list of apps.

Error message

No app set up to handle this file type.

Expected behaviour

Would be nice to have to choose what app to use when NX app doesn't know how to deal with it.

Steps to reproduce

1. Try to open YAML file (which is a simple text file) in NX app.
2. 
   
   
   3.
   

Environment data

Android version: 9

Device model: OnePlus A5010

Stock or customized system: no major changes applied

Nextcloud app version: 3.9.2 (usually latest - auto-updates ON)

Nextcloud server version: 16.0.6 (production stream)

Screenshot

[AndyScherzinger]

@tobiasKaminsky how do we want to handle this? When we can't detected the mime type we can just launch for "file" which won't give you a useful set of applications...

While for .yaml and others I'd be just fine to add them (doesn't solve the issue with unknown/undetctable types)

[stale[bot]]

This request did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

[AndyScherzinger]

pinging @tobiasKaminsky for feedback

[monperrus]

I just hit this bug and error message.

It happens for kbdx files (KeePass). It worked perfectly before and KeePassDroid is still installed.

Is there a known workaround on the client-side (phone) or on the server-side?

[AndyScherzinger]

@monperrus we didn't change anything on the Nextcloud side. For a workaround I usually suggest using KeePass2Android which is an android app having a dav client, so keepass2android itself is keeping your KeePass database in sync with the Nextcloud.

[AndyScherzinger]

You could test the QA build in #5326 to be sure

[monperrus]

we didn't change anything on the Nextcloud side.

do you mean on the client side?

FYI, the regression seems to coincide with a server upgrade from 16.x to 18.x

[monperrus]

I usually suggest using KeePass2Android which is an android app having a dav client, so
keepass2android itself is keeping your KeePass database in sync with the Nextcloud.

Thanks for the suggestion, I'll try this.

[AndyScherzinger]

do you mean on the client side?

Yes, no changes on the client side

FYI, the regression seems to coincide with a server upgrade from 16.x to 18.x

Interesting, while I am not aware of any change that might cause this though upgrading 2 mayor versions might have some changes relevant to this case.

[monperrus]

Who is responsible for setting the mime-type of the file based on the extension, the client or the
server?

[tobiasKaminsky]

This depends:

• open file online in text/OnlyOffice: we get matching mimetypes from server
• open files within our app, .eg. download markdown: we match in client
• open files with another app, e.g. keepass: Android is responsible of it: other apps register themselves centrally and Android shows a matching list.

[stale[bot]]

This request did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

[cieska]

Hopefully there will be some changes in future and I will leave this to be closed in two weeks. Thanks guys for you work..

[AndyScherzinger]

@cieska I'll tested the latest master build and it works fine for me as in:

• yml files get opened by the markor app directly (so that might work for you too
• kdbx files get opened by keepass2android

so both file types mentioned in this issue are actually resolved.

[jgoerzen]

Hi all,

I've been experiencing this same issue after upgrading to server v18, with KeePassDroid. This is a pretty severe issue for me. Do I understand correctly that a patch is checked in on this? If so, is there an ETA for the build appearing on the play store?

FWIW, it would also be nice to have a "download" option so a file could just be saved in the Downloads folder, as with a web browser, and then opened from there.

[AndyScherzinger]

@jgoerzen this is rather related to KeePassDroid I am afraid. It works just fine for keepass2android so no patch or anything since there is no issue on the Nextcloud side.

[jgoerzen]

I submitted a KeePassDroid bug and can confirm it works with keepass2android. https://github.com/bpellin/keepassdroid/issues/391

I'm confused though. I upgraded Nextcloud Server from 16 to 18, made no change on Android, and now my .kdbx files are useless on Android; I can't open them in KeePassDroid, can't save them, can only "send" them with some apps (Gmail, etc... don't want to send something security-sensitive like that).

Shouldn't there be a "save to Downloads" or some such option here?

[AndyScherzinger]

We don't have a download option, while the client downloads the file and stores it in its own data path.

Other than that without using KeePassDroid, so I can't say much about it, I am using KeePass2Android since it offers WebDav, so keepass2android is actually managing my kdbx file on the Nextcloud server it self and syncs changes back and forth (which is likely what you would also like to have).

[AndyScherzinger]

See also https://github.com/bpellin/keepassdroid/pull/352

[monreal]

I'm confused though. I upgraded Nextcloud Server from 16 to 18

Same here, only difference is that my server was upgraded from 17 to 18

[AndyScherzinger]

@tobiasKaminsky did we change anything (an in reading a server side detected mime type I am not aware of?)