Android Chrome - Uncaught (in promise) DOMException: Could not start video source

[adambadge]

Again thank you so much for such a wonderful plugin. It works flawlessly on my desktop. I am however having an issue on mobile. The camera does not appear to start up. It simple spins the loading.

I was able to perform remote debugging and the error message in the remote chrome console reads:

Uncaught (in promise) DOMException: Could not start video source

Environment details
APEX-QR_Code-Scanner version: 1.5.1.0
Galaxy Note10+ 5G
Android 10 base
Android chrome browser: 89.0.4389.105

I have tested this on multiple APEX apps and your example site below and all give the same error.

Any help would be greatly appreciated!

[RonnyWeiss]

Hello

This occurs only when camera usage is blocked or camera is used by any other app on your computer e.g. zoom, teams or another browser tab. Please clarify this. I will implment a better warning message when this occur in next version.

Kind regards

Ronny

[adambadge]

Thank you for the speedy response, I restarted my phone closed all chrome tabs, closed all apps and reviewed running apps and unfortunately I am still receiving the same error.

I then found a website that allows testing of the camera in the browser and it worked fine.

I'm not sure if this is important but the camera test website I went to gave me a drop down of options to chose the camera:

• Camera2 1, facing front
• Camera2 3, facing front
• Camera2 4, facing back
• Camera2 2, facing back
• Camera2 0, facing back

Is the plugin defaulting to a particular camera? and could an option be added to select a camera?

Many thanks,
Adam

[RonnyWeiss]

this is the facing mode! It can be set in configJSON in Plug-in attributes. Could you please check that.

Smartphone cameras made me a heavy life because then have so many cameras and I could not test all phones :-)

[adambadge]

Hi Ronny,

My config.js looks like the below, is there a different value I should change facingMode to test?

{
"height": 340,
"scanFrameColor": "rgba(192,0,15,1)",
"facingMode": "environment",
"mirrorScanner": false
}

I'm new to this but reading a couple of StackOverflow posts suggests facingMode "environment" SHOULD work but doesn't appear to always work under some environments.

This post suggests ways to select the camera by ID in Javascript https://stackoverflow.com/questions/59636464/how-to-select-proper-backfacing-camera-in-javascript.

[RonnyWeiss]

could you please try another facing mode in plug-in configuration and recheck if it works. I tried it also on my A70 with Android 11 and latest chrome and it works as it should.

The implementation is cross browser compatible so I think it's a very special problem. hope we can debug it.

I use it like:

https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia

[adambadge]

Hi Ronny,

I testing the facingMode "user" with now change.
Reviewing the console error on remote debugging does point to this function.

This might be a Galaxy S10 thing.

[RonnyWeiss]

could you try another browser on your phone or a different phone?

[adambadge]

Yep can do, will provide an update shortly

[RonnyWeiss]

thank you! and thank you so much for your donation! Hope we can fix the problem!

[adambadge]

Hi Ronny,

I was able to test on a different phone and it works great. I have also now for it working on Firefox, it appears to be a unique problem with my Chrome.

[RonnyWeiss]

It annoys me personally that we don't have a solution, but I'm not aware of anything like that that could cause the error. You haven't tried another browser on the S10, have you?
Should I close the ticket for now?