The Chime SDK for JavaScript invokes the device-label-trigger function when the device label is blank, such as in a private window. By default, the SDK requests access to both the microphone and camera to retrieve device labels. If either or both of these requests fail, the SDK will send a new meeting event deviceLabelTriggerFailed. (Before this PR, the SDK would emit audioInputFailed and videoInputFailed events simultaneously, which could lead to confusion.)
If a custom function is provided via meetingSession.audioVideo.setDeviceLabelTrigger, the SDK will send this event if the custom function is unsuccessful.
Testing:
Can these tested using a demo application? Please provide reproducible step-by-step instructions.
Yes.
Open the Chime SDK Serverless Demo in a private window, such as the Chrome Incognito window.
Open the browser console.
Enter your meeting title and name, then select the Continue button.
When the browser requests for mic and camera permission, deny it.
Confirm that the SDK sends the deviceLabelTriggerFailed event to the browser console.
Checklist:
Have you successfully run npm run build:release locally?
Yes.
Do you add, modify, or delete public API definitions? If yes, has that been reviewed and approved?
No.
Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved?
No.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Issue #: N/A
Description of changes:
The Chime SDK for JavaScript invokes the device-label-trigger function when the device label is blank, such as in a private window. By default, the SDK requests access to both the microphone and camera to retrieve device labels. If either or both of these requests fail, the SDK will send a new meeting event
deviceLabelTriggerFailed. (Before this PR, the SDK would emitaudioInputFailedandvideoInputFailedevents simultaneously, which could lead to confusion.)If a custom function is provided via
meetingSession.audioVideo.setDeviceLabelTrigger, the SDK will send this event if the custom function is unsuccessful.Testing:
Can these tested using a demo application? Please provide reproducible step-by-step instructions.
Yes.
deviceLabelTriggerFailedevent to the browser console.Checklist:
Have you successfully run
npm run build:releaselocally? Yes.Do you add, modify, or delete public API definitions? If yes, has that been reviewed and approved? No.
Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved? No.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.