-
Notifications
You must be signed in to change notification settings - Fork 286
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
Video Constraints Props Doesn't Work in Mobile Device but Works Fine in Web and Web Responsive Simulator #370
Comments
Same for me, but not only with aspect-ratio, but with specifying height and width. Note that this works on mobile Firefox but not on mobile chrome |
I'm having this same issue, how did you guys handle this |
I haven't dealt with it so far, but next thing would be using a different camera library I guess 😞 |
What library, I think its not a library thing, but something with the constraints |
I now fiddled with custom options via the getUserMedia
) In the past we had a full-screen camera dialog, which it seems isn't possible anymore.. To find constraints that fit to your usecase i recommend you reading through following links and playing around with the options: |
I also had the same issue and then realised that it was because the default orientation for desktop was landscape, while mobile was portrait. So in the end I was able to make it work for both platforms by swapping the width and height constraints depending on device type. For example:
|
Please follow the general troubleshooting steps first:
Bug reports:
I tried the videoConstraints with
aspect-ratio 9 / 16
in web and responsive simulator in web and it works fine, but when open it in mobile device (android), the resolution of react-webcam video isnt 9 / 16 (back to default resolution of react-webcam). Any ideas how to make it works in mobile device?Features:
Please note by far the quickest way to get a new feature is to file a Pull Request.
We will consider your request but it may be closed if it's something we're not actively planning to work on.
The text was updated successfully, but these errors were encountered: