Open with does not force app chooser about amazefilemanager HOT 8 CLOSED

Force Chooser dialog comes once you choose "Other" from the Open with dialog.
The open with dialog just makes it easy for you by not going through the long list of all apps. Otherwise you can always choose to open according to your own using other option

from amazefilemanager.

You aren't understanding.
The issue is that the open with dialog does not show once you have selected an item and flagged it to always use that handler.

Edit: The expected behavior is that when you "just click" on a file, it will launch the handler that it is set to "always use", and when you select "open with", it would force chooser.

Right now you aren't using proper intents/intent filters to launch the integrated file handlers (text file, zip file, etc.), which means that by default, it will try to use the integrated file handlers, and that open with gives a roundabout way to bypass that. If you bring it back one step so that your integrated handlers respond the same way as other user-installed file handlers, then you achieve the expected behavior.

from amazefilemanager.

Your issue is expected to be solved with latest commit. At least for text files. Zip files will still be preferred to be opened directly in app only. Still you can use "open with " for them

from amazefilemanager.

Ok.

I see the switch to openunknown. I don't see a change to long-press-->open-with using force-chooser.

What is the rationale for keeping zip files handled internally? Presumably, if the user has installed an alternative zip file handler, they would have installed it because they prefer to use it.

from amazefilemanager.

Here, I think this should do it; lbdroid/AmazeFileManager@485de2c

Note: I have NOT created a pull request, because I am not in a position right now to compile/test it.

from amazefilemanager.

Zip viewing was preserved so the animations work fine. I don't know why but fragment transitions don't animate in new activity. I will look into that commit

from amazefilemanager.

You should be able to use Intent.resolveActivity(PackageManager) or PackageManager.resolveActivity(Intent, MATCH_DEFAULT_ONLY) to detect if we are the default handler, and then transition the fragment directly.

from amazefilemanager.

I've been able to test that commit now, and it works exactly as expected, so I have created a pull request. When you click on a file, it will launch the default handler, or show chooser if there is no set default. When you long-click --> menu --> open with, it ALWAYS forces the chooser.

from amazefilemanager.