Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doesn't work on older android versions supported by flutter 16+ #25

Closed
phaylali opened this issue Jan 5, 2019 · 7 comments
Closed

doesn't work on older android versions supported by flutter 16+ #25

phaylali opened this issue Jan 5, 2019 · 7 comments

Comments

@phaylali
Copy link

phaylali commented Jan 5, 2019

No description provided.

@miguelpruivo
Copy link
Owner

Can you be clear about which version you’re referring to?

@phaylali
Copy link
Author

phaylali commented Jan 5, 2019

16 17 18, since api level 19 uses WRITE_EXTERNAL_STORAGE only , may beadding READ_EXTERNAL_STORAGE will make the plugin work on 16 17 18 api levels ?

@miguelpruivo
Copy link
Owner

Can you fork it and give it a try? I’m not able at the moment. If it works make a PR.

Thank you.

@phaylali
Copy link
Author

phaylali commented Jan 5, 2019

okay I will try

@phaylali
Copy link
Author

phaylali commented Jan 8, 2019

didn't help , android 16 17 18 are not working with this plugin

@phaylali
Copy link
Author

I found a solution , it is a problem with android itself , below android 5 lollipop , phones have Downloads app not File Manger app , so to use apps that use this plugin , the phone needs to have a file manager like ES File Manager , I'm gonna close this issue since I found a solution

@miguelpruivo
Copy link
Owner

miguelpruivo commented Jan 10, 2019

Yes, thank you for pointing that. I forgot to mention that the phone always need a FileExplorer to handle the intent that is made, after api 19 there is a native explorer provided with Android which should always be the preferred one for this plugin. I'll probably add this to the readme.

There are however, one issue reported from an user that has a custom FileProvider from a custom rom (I believe a lenovo rom from a Moto phone) which somehow won't provide the correct path neither will open the native explorer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants