The askDevicePermission API takes too long
The askDevicePermission
API prompts the end user via the browser asking if they allow permission to use camera or microphone.
If the end user approves camera or microphone usage, then those devices are available to be used in a call. The devices availability is reflected in available device list.
User taking a long time to approve the permission can cause delay in the API response.
Occasionally, the device list update step can take a long time. A delay in the driver layer is usually the cause of the issue. The issue can happen with some virtual audio devices in particular. Chromium Issue 1402866
How to detect using the SDK
To detect this issue, you can measure the time difference between when you call the askDevicePermission
API and when the promise resolves or rejects.
How to mitigate or resolve
If the askDevicePermission
API fails due to the user not responding to the UI permission prompt,
the application can retry the API again and the user should see the UI permission prompt.
As for other reasons, such as the device list updating taking too long to complete, the user should check their devices and see if there's any device that could potentially be causing this issue. They may need to update or remove the problematic device to resolve the issue.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for