-
Notifications
You must be signed in to change notification settings - Fork 614
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
bug(camera): Camera.requestPermissions() hangs on Android 33+ #2140
Comments
This issue needs more information before it can be addressed. In particular, the reporter needs to provide a minimal sample app that demonstrates the issue. If no sample app is provided within 15 days, the issue will be closed. |
This comment was marked as abuse.
This comment was marked as abuse.
Hello, |
We are experiencing the same issue. Any updates? |
So if you remove the But the |
Is it safe to use without requesting permissions to read from camera/gallery, I thought it should always ask the user. |
Capacitor Version
6
Other API Details
No response
Platforms Affected
Current Behavior
When I click the button to pick an image from the gallery nothing happens
Expected Behavior
When i click the button to pick an image from the gallery it shows a pop-up to allow reading images and then select the image
Project Reproduction
https://github.com/stefanMinch3v/capacitor-bug-image-gallery/tree/main
Additional Information
On capacitor 5 the code below works as expected. It requests permission to read from gallery and then shows the gallery to pick an image. With capacitor 6, on button click nothing happens
With only these 2 permissions in the AndroidManifest.xml file
uses-permission android:name="android.permission.READ_MEDIA_IMAGES"
uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"
Android version tested - 12 (works here), 13 (not working) and 14 (not working)
`async selectImage(): Promise {
}`
Any idea how should I proceed here, do I need to add some extra code or permissions to the manifest file?
Thank you
The text was updated successfully, but these errors were encountered: