Rear Camera Selection on Mobile Devices (Zoom Web SDK v3.6.0)

Meeting SDK Web
1

Description
I’m working with the Zoom Web SDK (v3.6.0) and have noticed that rear-camera functionality seems to be completely missing for mobile devices. Here’s what I’ve observed:

  1. On mobile devices (e.g., iPhone, Android), the interface allows switching to the rear camera, but selecting it does nothing.
  2. When checking the settings, only the front camera appears in the dropdown menu.
  3. After reviewing the codebase, there doesn’t appear to be any logic implemented to support rear-camera functionality.

Browser Console Error
No errors as I am doing research trying to determine whether it’s worth introducing new code to support this feature or if leaving it as-is is the best approach. Any advice or insights you could provide would be greatly appreciated.

Which Web Meeting SDK version?
v3.6.0

Meeting SDK Code Snippets
No code snippets as there were no errors

To Reproduce(If applicable)
Steps to reproduce the behavior:

  1. Open the Zoom Web SDK on a mobile device (tested on iPhone 18 with the latest updates).
  2. Attempt to switch to the rear camera using the video icon arrow interface.
  3. Check the settings to see available camera options.
  4. Attempt to select the rear camera and observe that nothing happens.

Screenshot 1
Showing the settings interface with only the front camera available.
Link:
[Screen Shot 1]
uploads/zoomdeveloper/original/3X/a/3/a397977d95da8beb0a4bf27f8e76efc9dd844976.png

Screenshot 2
Showing the attempt to select the rear camera, which does not trigger the event to change to the rear.
Link:
[Screen Shot 2]
uploads/zoomdeveloper/original/3X/6/7/6785e5cc0ca45d5f116f4e88ca15509cec8dae3e.png

Troubleshooting Routes
I have tested the functionality across multiple browsers on the latest iPhone (Safari, Edge, and Chrome) and observed the same behavior in each.

Device Information:

  • Device: iPhone 18
  • OS: Latest iOS version
  • Browsers:
    • Safari Version: 18.1
    • Chrome Version: 132.0.0
    • Edge Version: 132.0.2957.122

Additional context
I’m trying to determine whether it’s worth introducing new code to support this feature or if leaving it as-is is the best approach. Any advice or insights you could provide would be greatly appreciated.

2

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.