camState and micState from useDevices() are set to "granted" before permissions are requested

[rileyjshaw]

Expected behavior

useDevices().camState and useDevices().micState should be set to "pending" or "unknown" until device access is requested and granted.

Describe the bug (unexpected behavior)

When a call is created with startAudioOff and startVideoOff set to true, then joined, useDevices().camState and useDevices().micState return "granted" even before device access is requested with callObject.updateParticipant('local', { setVideo: true, setAudio: true }).

Steps to reproduce

Initialize the call with startAudioOff and startVideoOff set to true:

const callObject = DailyIframe.createCallObject({
	startAudioOff: true,
	startVideoOff: true,
	// ...
});

Join the call:

await callObject.join({ url: dailyRoomUrl, token: dailyMeetingToken, userName: name });

Later (but before calling callObject.updateParticipant), run the following:

const { camState, micState } = useDevices();
console.log(camState, micState); // > granted granted

System information

• Device: Macbook Pro M1 Max, 2021
• OS, version: MacOS Ventura 13.1
• Browser, version: 109.0b2 (64-bit)

Additional context

I’m currently using the following as a workaround:

const { cameras, microphones } = useDevices();
const isMediaAccessGranted =
	cameras.some(c => c.selected && c.state === 'granted') &&
	microphones.some(m => m.selected && m.state === 'granted');

[Regaddi]

Thanks @rileyjshaw for the bug report!

I'll investigate the issue today and will let you know about any updates.

[Regaddi]

Update

I have opened a PR which introduces a new device state "idle", which becomes the new default state.
For rooms configured with cam and mic off, the state will remain in "idle" until the first call to getUserMedia, which switches the state to "pending" and eventually to "granted", "blocked" or any of the other possible error states.

With that "pending" gets a clearer meaning as it maps to a pending getUserMedia call.

I decided to not use "unknown" for the described case, as the state is generally known and "unknown" is already defined as a state to represent an "unknown error".

The plan is to push out a release today or Monday, which will include this and some other fixes and improvements (e.g. #6 and #9).

[rileyjshaw]

Fantastic!! I love the idea of introducing an "idle" state, that makes a lot of sense. Thanks for all the work, and for being so quick to respond here 😊

[Regaddi]

This change has shipped with daily-react 0.7.0 today!

[rileyjshaw]

Yahooo, thank you!