# Chrome issue getting devices

**URL:** https://openvidu.discourse.group/t/chrome-issue-getting-devices/2455
**Category:** Issues developing apps
**Tags:** v2
**Created:** [December 17, 2020, 4:33pm UTC](https://openvidu.discourse.group/t/chrome-issue-getting-devices/2455 "2020-12-17T16:33:53Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![pabloFuente](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/pablofuente/32/2536_2.png) [@pabloFuente](https://openvidu.discourse.group/u/pabloFuente)
#### Post date: [June 22, 2021, 11:23am UTC](https://openvidu.discourse.group/t/chrome-issue-getting-devices/2455/3 "2021-06-22T11:23:26Z")

</div>

This is the Web API telling you that the “deviceId” property used in method [**`navigator.mediaDevices.getUserMedia`**](https://developer.mozilla.org/es/docs/Web/API/MediaDevices/getUserMedia) is violating the supported values. That “deviceId” property is finally used by openvidu-browser in the [MediaTrackConstraints](https://developer.mozilla.org/en-US/docs/Web/API/MediaTrackConstraints) object to init the audio or video source. And it is doing so with the “exact” option, so if the deviceId is not supported as a valid audio or video input device, it will fail with that error.

To sum it up: you are probably passing as `audioSource` or `videoSource` in your PublisherProperties configuration object an invalid `deviceId`.

Cheers.

---

_[View the full topic](https://openvidu.discourse.group/t/chrome-issue-getting-devices/2455)._
