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

The file picker in Android 14 is not working and is prompting for memory access permission. This issue occurs in an application that was previously running without problems. #1560

Closed
alok511 opened this issue Jul 24, 2024 · 5 comments
Labels
new issue An issue that hasn't yet been seen from the maintainer stale

Comments

@alok511
Copy link

alok511 commented Jul 24, 2024

Package file_picker:linux references file_picker:linux as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of file_picker to either avoid referencing a default implementation via platforms: linux: default_package: file_picker or add an inline implementation to file_picker via platforms: linux: pluginClass or dartPluginClass.

@alok511 alok511 added the new issue An issue that hasn't yet been seen from the maintainer label Jul 24, 2024
Copy link

github-actions bot commented Aug 1, 2024

This issue is stale because it has been open for 7 days with no activity.

@github-actions github-actions bot added the stale label Aug 1, 2024
@gnprice
Copy link

gnprice commented Aug 1, 2024

The issue with that error message is tracked already as #1555.

The issue title sounds like a different issue. Perhaps #1559? Quoting the error message would help.

@github-actions github-actions bot removed the stale label Aug 2, 2024
@aptexd
Copy link

aptexd commented Aug 4, 2024

I also have the same confusion, the same code, I can read the file on Android 13, but I can't get it on Android 14

Copy link

This issue is stale because it has been open for 7 days with no activity.

@github-actions github-actions bot added the stale label Aug 12, 2024
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new issue An issue that hasn't yet been seen from the maintainer stale
Projects
None yet
Development

No branches or pull requests

3 participants