# iOS looping/constant failover **URL:** \ **Category:** Web\ **Tags:** video-sdk\ **Created:** [July 25, 2025, 1:25pm UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667 "2025-07-25T13:25:10Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![unfounded-raccoon](https://avatars.discourse-cdn.com/v4/letter/u/f04885/32.png) [@unfounded-raccoon](https://devforum.zoom.us/u/unfounded-raccoon)\ **Post date:** [July 25, 2025, 1:25pm UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/1 "2025-07-25T13:25:11Z")
**Description** Hey all, we’re seeing occasional issues with our users on iOS where the user gets stuck in a permanent looping/reconnecting state. This is reproducible in the test/sample app. **Browser Console Error** The full error message or issue you are running into. **Which Web Video SDK version?** 2.2.5 **Video SDK Code Snippets** Nothing specific needs to be done, just use the sample app. **To Reproduce(If applicable)** Steps to reproduce the behavior: 1. Run the sample app on iPhone 16, using Safari, iOS 18; not all devices show the problem, we haven’t narrowed it down that far yet, BUT the exact problem does reproduce when using BrowserStack’s “iPhone 16, Safari 18.5” browser. In case you’re tempted to think it’s a browserstack problem, it works fine on the same phone running Chrome (which is technically webkit, I know). **Screenshots** **Troubleshooting Routes** Completely reproducible on browserstack using the sample app + Safari. Using Chrome on the exact same device does not exhibit the same problems, so it seems like something is being detected incorrectly in the Safari version. Note that we have this problem on non-browserstack devices also, it’s just 100% replicable there. **Device (please complete the following information):** - Device: iPhone - OS: 18.5 - Browser: Safari - Browser Version 18.5 **Additional context** It seems to get stuck in failover/out of failover looping. So something is triggering a failover when it shouldn’t, at least as far as I can tell. If you can determine the difference in the flow on Chrome for iOS vs Safari for iOS, that should get to the root problem. ---
**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\ **Post date:** [July 25, 2025, 2:23pm UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/2 "2025-07-25T14:23:14Z")
Hey @unfounded-raccoon Thanks for your feedback. Could you share some problematic session IDs with us for troubleshooting purposes? Thanks Vic ---
**Author:** ![unfounded-raccoon](https://avatars.discourse-cdn.com/v4/letter/u/f04885/32.png) [@unfounded-raccoon](https://devforum.zoom.us/u/unfounded-raccoon)\ **Post date:** [July 25, 2025, 2:44pm UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/3 "2025-07-25T14:44:34Z")
isInMeeting: true password: “” sessionId: “+4xy4tz1Sl+TRMZy+s6bEg==” topic: “topic” userId: 17401856 userName: “Safari-813” ---
**Author:** ![unfounded-raccoon](https://avatars.discourse-cdn.com/v4/letter/u/f04885/32.png) [@unfounded-raccoon](https://devforum.zoom.us/u/unfounded-raccoon)\ **Post date:** [July 25, 2025, 4:51pm UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/4 "2025-07-25T16:51:01Z")
Here’s another if it helps: isInMeeting: true password: “” sessionId: “yKEyTzW2QrqC0yobFpRNSg==” topic: “topic” userId: 16783360 userName: “Safari-556” ---
**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\ **Post date:** [July 28, 2025, 2:39am UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/5 "2025-07-28T02:39:07Z")
Hey @unfounded-raccoon > +4xy4tz1Sl+TRMZy+s6bEg== > yKEyTzW2QrqC0yobFpRNSg== We tested on the BrowserStack and did observe constant failover issues, which are caused by unexpected socket disconnections triggering failover. However, we also tested on a real iOS 18.5 device and were not able to reproduce the issue there. Thanks Vic ---
**Author:** ![unfounded-raccoon](https://avatars.discourse-cdn.com/v4/letter/u/f04885/32.png) [@unfounded-raccoon](https://devforum.zoom.us/u/unfounded-raccoon)\ **Post date:** [July 28, 2025, 12:00pm UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/6 "2025-07-28T12:00:17Z")
I understand, however this does occur (occasionally) on other iOS devices as well - exact same symptoms. And Chrome (on iOS) does NOT have the symptoms. The user that initially reported this to me explicitly stated that they were using an iphone + safari, and after switching to Chrome, the problem went away. ---
**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\ **Post date:** [July 29, 2025, 1:33am UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/7 "2025-07-29T01:33:39Z")
Hi @unfounded-raccoon That’s strange — Chrome on iOS is also based on WebKit, and this should remain the same even in the EU region. Thanks Vic ---
**Author:** ![unfounded-raccoon](https://avatars.discourse-cdn.com/v4/letter/u/f04885/32.png) [@unfounded-raccoon](https://devforum.zoom.us/u/unfounded-raccoon)\ **Post date:** [July 29, 2025, 12:20pm UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/8 "2025-07-29T12:20:40Z")
No disagreement here, which is why it was super weird that in browserstack, Chrome works when Safari doesnt, on the same device. That screams to me that there’s something else going on. And again, this replicates for ACTUAL devices too, this is the exact experience my customer had - Safari (on a regular iphone) failed, switched to Chrome, and it worked. ---
**Author:** ![unfounded-raccoon](https://avatars.discourse-cdn.com/v4/letter/u/f04885/32.png) [@unfounded-raccoon](https://devforum.zoom.us/u/unfounded-raccoon)\ **Post date:** [July 31, 2025, 1:39pm UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/9 "2025-07-31T13:39:52Z")
Is there anything I can do to help you guys diagnose this one further? ---
**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\ **Post date:** [August 1, 2025, 2:07am UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/10 "2025-08-01T02:07:50Z")
Hey @unfounded-raccoon Could you share some problematic session IDs from actual devices with us for troubleshooting purposes? Thanks Vic ---
**Author:** ![unfounded-raccoon](https://avatars.discourse-cdn.com/v4/letter/u/f04885/32.png) [@unfounded-raccoon](https://devforum.zoom.us/u/unfounded-raccoon)\ **Post date:** [August 4, 2025, 3:30pm UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/11 "2025-08-04T15:30:42Z")
You bet. 9h6YIIm/Qum33iyPYbqd3Q== You’ll see they “joined the session” (but were kicked out) 62 times in a row. ---
**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\ **Post date:** [August 5, 2025, 2:41am UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/12 "2025-08-05T02:41:45Z")
Hi @unfounded-raccoon > 9h6YIIm/Qum33iyPYbqd3Q== This behavior is quite similar to what we observed on BrowserStack. From the logs, the constant failover was caused by an unexpected socket disconnection with the server. We will optimize for this in the next version. It will be available in late August. Thanks Vic ---
**Author:** ![unfounded-raccoon](https://avatars.discourse-cdn.com/v4/letter/u/f04885/32.png) [@unfounded-raccoon](https://devforum.zoom.us/u/unfounded-raccoon)\ **Post date:** [August 5, 2025, 2:10pm UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/13 "2025-08-05T14:10:47Z")
Thanks Vic, great to hear. ---
**Author:** ![Dungvl76](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/dungvl76/32/49218_2.png) [@Dungvl76](https://devforum.zoom.us/u/Dungvl76)\ **Post date:** [September 11, 2025, 2:57am UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/14 "2025-09-11T02:57:26Z")
Hi @vic.yang Could you please help me check if the session below is experiencing the same issue? Currently, there is only one user in the session, but the system recorded that this user joined and left more than 80 times. Could this be caused by the client repeatedly receiving the `reconnecting` and `connected` events? SessionId: DCbwdBxARmiT4HLkVloqLg== Thanks for your support. ---
**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\ **Post date:** [September 11, 2025, 3:15am UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/15 "2025-09-11T03:15:32Z")
Hey @Dungvl76 Thanks for your feedback. > DCbwdBxARmiT4HLkVloqLg== Indeed, the constant failover was caused by an unexpected socket disconnection with the server. Thanks Vic ---
**Author:** ![Alexandru](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/alexandru/32/51213_2.png) [@Alexandru](https://devforum.zoom.us/u/Alexandru)\ **Post date:** [November 27, 2025, 4:03pm UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/16 "2025-11-27T16:03:06Z")
Hello ! I had the same issue recently on the latest Safari. Chrome on IOS is working as expected, while Safari is constantly changing failover. Was the error solved? ---
**Author:** ![Edith1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/edith1/32/72506_2.png) [@Edith1](https://devforum.zoom.us/u/Edith1)\ **Post date:** [November 27, 2025, 6:53pm UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/17 "2025-11-27T18:53:55Z")
**Description** Hey all, we’re seeing occasional issues with our users on iOS where the user gets stuck in a permanent looping/reconnecting state. This is reproducible in the test/sample app I am sharing here shorturl.at/u6AsB. > [@unfounded-raccoon](#): > > **Browser Console Error** > The full error message or issue you are running into. > > **Which Web Video SDK version?** > 2.2.5 > > **Video SDK Code Snippets** > Nothing specific needs to be done, just use the sample app. > > **To Reproduce(If applicable)** > Steps to reproduce the behavior: > > 1. Run the sample app on iPhone 16, using Safari, iOS 18; not all devices show the problem, we haven’t narrowed it down that far yet, BUT the exact problem does reproduce when using BrowserStack’s “iPhone 16, Safari 18.5” browser. In case you’re tempted to think it’s a browserstack problem, it works fine on the same phone running Chrome (which is technically webkit, I know). > > **Screenshots** > > **Troubleshooting Routes** > Completely reproducible on browserstack using the sample app + Safari. Using Chrome on the exact same device does not exhibit the same problems, so it seems like something is being detected incorrectly in the Safari version. > > Note that we have this problem on non-browserstack devices also, it’s just 100% replicable there. > > **Device (please complete the following information):** > > - Device: iPhone > - OS: 18.5 > - Browser: Safari > - Browser Version 18.5 > > **Additional context** > It seems to get stuck in failover/out of failover looping. So something is triggering a failover when it shouldn’t, at least as far as I can tell. If you can determine the difference in the flow on Chrome for iOS vs Safari for iOS, that should get to the root problem. Thanks for the detailed breakdown — this definitely looks like a Safari-specific failover loop, since Chrome on the same iOS build behaves fine. If you’ve captured logs or a quick screen recording, share it,so the team can compare the flows more clearly. ---
**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\ **Post date:** [November 28, 2025, 1:02am UTC](https://devforum.zoom.us/t/ios-looping-constant-failover/135667/18 "2025-11-28T01:02:18Z")
Hi @Alexandru @Edith1 It’s a known issue on iOS Safari 26, and we have reported the issue to Apple. > [@iOS 26.1 Issue Connecting and joining call on Safari](https://devforum.zoom.us/t/ios-26-1-issue-connecting-and-joining-call-on-safari/138935): > > 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 upg… Thanks Vic