-
Notifications
You must be signed in to change notification settings - Fork 1k
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 plugin requires users to edit the photo first even though edit is set to disabled #2210
Comments
Steps to reproduce (Huawei Nova)
|
I can't reproduce on my devices, can you provide a sample app just in cases something is different from the code you shared here? Also, would be good to know android version of the device and if only happens in that one (if you tested more) |
I can duplicate this as well on a SAMSUNG-SM-J327A Android 7.0 physical device as well as in the simular on a Pixel 3a running API 29.
async takeAPhoto() {
} |
Also, this looks to be the same as #2020 |
closing since the reporter didn't answer. For the "losing photo if you cancel" bug, that's fixed already. |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Capacitor, please create a new issue and ensure the template is fully filled out. |
Bug Report
Capacitor Version
npx cap doctor
output:Affected Platform(s)
Current Behavior
Expected Behavior
Sample Code or Sample Application Repo
Reproduction Steps
Android phone with ionic capacitor app, allow user 2 methods in the controller 1 for taking a new photo and 1 for taking from gallery. User selects either take photo or from gallery and it only sends if they edit the photo they just took in the photos app and add a filter and click save - expected result as was working with the cordova previously is to just select or take a photo and it will send directly to the apps interface.
Issue most prevalent on Android, IOS still asks you to edit the image before sending also but its less of a hassle and feels more native.
Other Technical Details
npm --version
output:6.9.0
node --version
output:v10.16.0
The text was updated successfully, but these errors were encountered: