This message was deleted.
# helpdesk
s
This message was deleted.
b
The reason this matters is for my users -- if they happen to have continuity camera enabled they will open my app and not see any video (seemingly broken) until they go to the camera selection menu to choose the built-in camera. To serve ux, the built-in camera should always be the default then let implementers override from there...
d
This is a great point @boundless-salesclerk-13461. CC @freezing-lifeguard-43174 on this one
✅ 1
b
thanks @dry-elephant-14928 hi @freezing-lifeguard-43174 👋 Any thoughts on this?
f
ah, maybe need to detect the camera type is continuity, so as to skip it when selecting the default camera, Or when the user is opening a continuity camera, but does not receive a video frame, prompt to go to their iPhone and click allow connection
we can know the camera type is Continuity Camera at the native level, Perhaps an additional type field can be added to macOS Video Device https://developer.apple.com/documentation/avfoundation/avcapturedevice/4024614-iscontinuitycamera
b
@freezing-lifeguard-43174 thanks for the reply, where's the default camera selection done in the dart lib? I'll take a closer look there but wasn't able to locate the code when I looked for it a few days ago.
d
@freezing-lifeguard-43174 maybe for now we can bypass continuity camera when selecting a default camera?
f
This may need to be done from the native layer, let me do some testing
👍 2