iOS 26.1 Issue Connecting and joining call on Safari

We’re experiencing an issue joining and staying connected to a call on Safari iOS with the latest iOS update. After accepting permissions, the video never appears locally and the user is stuck in a reconnecting state and the call never actually connects.

The issue is on Safari iOS only, Chrome on iOS works fine.

Video SDK Version: 2.2.5
Platform iOS
OS Version 26.1 23B85
Browser Safari Mobile
Device iPhone 16

Steps to reproduce:

  • Try to join a call on Safari IOS using a phone that is upgraded to iOS 26.1 23B85
  • Accept permissions and observe that you are never connected to the call and video is also not displayed

Additionally, we see the following failed requests reported by DataDog. Seems like ping is failing to multiple locations:

Fetch error GET:rwciad2.iad.zoom.us/wc/ping/93457184730?ts=1764007650003
Fetch error GET:rwcsjc2.sjc.zoom.us/wc/ping/93457184730?ts=176400765000
Fetch error GET:rwcsjc3.sjc.zoom.us/wc/ping/93457184730?ts=1764007650003

Hey @mk352

Thanks for your feedback.

I would like to check whether you are using iCloud+ and have Privacy Relay enabled. If so, this is a known iOS issue, and we have already reported the bug to Apple. The current workaround is to temporarily disable iCloud+ Privacy Relay.

Thanks
Vic

@vic.yang I’m a colleague of @mk352 and have been tracking this issue over the last couple of months. It seems based on my correspondence with the Apple team in the linked WebKit bug report that this issue is nowhere close to being resolved by Apple.

Does Zoom have any alternative workarounds we could try? Do you guys have any plans to change the websocket connection workflow to allow private relay safari users to connect to Zoom calls?

It’s not feasible to ask users to turn off private relay or switch browsers as this is very cumbersome.

Thanks in advance for your reply,

Jon

Hi @JonV

Thank you very much for your enthusiasm and for helping us track Apple’s bug fix. At the moment, we don’t have a good workaround to address this issue in the short term.

We are also researching how to enable multi-channel WebSocket multiplexing to prevent similar issues, but this is still under research and development.

Thanks
Vic