-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
iOS 13 camera is not working as expected #492
Comments
I think there is a bug in iOS 13. |
@mevinDhun Technically your fix is correct, but I don't think is the best one because the metadata will not be included. On my app I use the camera with exif and in this case the exif data are missing. Today I fixed the issue completely, including the exif implementation. Here is the new implementation: vlinde/cordova-plugin-camera-with-exif@99465b4 |
Any chance their might be an ETA on this fix? |
I ran into this issue as well.
When I downloaded my app's package, I found that there were 2 images being created in the /tmp folder every time I took a picture. The first one had my picture and the second was empty. I installed @mevinDhun 's fork and it resolved the issue for me. Thank you Mevin!!! Tested on: |
@jfbloom22 did you try this on 13.1.3 |
How to install @mevinDhun 's fork ?The cmd is? |
@anubhavberry I did not test with 13.1.3. I was on one or two updates before that one. 13.1.1 or 13.1.2. @dythbj command is: |
Why is this fix not merged? |
Closed by #712 |
Bug Report
Problem
On iOS 13 the camera is not working as expected.
What is expected to happen?
To save the image with content in the temp folder and to return the location.
What does actually happen?
The image is saved and the plugin returns the path but the image content is missing.
Information
Command or Code
I use the following settings to open the camera.
When I use
camera.DestinationType.DATA_URL
instead ofcamera.DestinationType.FILE_URI
I get the base64 code.Environment, Platform, Device
Tested on iOS 13 beta 6 & 7.
Version information
Checklist
The text was updated successfully, but these errors were encountered: