# \[CRITICAL\] No Audio for mobile iOS browsers

**URL:** <https://devforum.zoom.us/t/critical-no-audio-for-mobile-ios-browsers/19721>\
**Category:** Web\
**Created:** [May 31, 2020, 9:55pm UTC](https://devforum.zoom.us/t/critical-no-audio-for-mobile-ios-browsers/19721 "2020-05-31T21:55:59Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![cquibada](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/cquibada/32/13063_2.png) [@cquibada](https://devforum.zoom.us/u/cquibada)\
**Post date:** [May 31, 2020, 9:55pm UTC](https://devforum.zoom.us/t/critical-no-audio-for-mobile-ios-browsers/19721/1 "2020-05-31T21:55:59Z")

</div>

**Description**  
Before, there was audio on iOS but can only be heard through earphones. But now, none can be heard at all!

**Error**  
N/A

**Which version?**  
1.7.8

**To Reproduce(If applicable)**

1. Load web sdk in mobile iOS device.
2. No audio can be heard

**Screenshots**  
N/A

**Smartphone (please complete the following information):**  
iPhone XR, iPhone 7, iPad

---

<div class="post-metadata">

**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\
**Post date:** [June 1, 2020, 12:36am UTC](https://devforum.zoom.us/t/critical-no-audio-for-mobile-ios-browsers/19721/2 "2020-06-01T00:36:39Z")

</div>

Hi @cquibada,

There is a limitation with using Computer Audio with iOS devices. Currently, Safari does not support the Audio worklet API which limits the use of Computer Audio for our WebSDK since we use Web Assembly instead of WebRTC[1].  
For other browsers on iOS such as Chrome, Edge, or Firefox, they have to use the same engine on iOS which is why they work on Android but not iOS.  
Currently, we are waiting for Apple’s Safari to adopt the Audio worklet API for us to enable computer audio. You can add a new discussion to Apple’s developer forum[2] suggesting them to to adopt the Audio worklet API similar to how Firefox adopted a couple weeks ago[3].

As soon as they enabled the API we will inform everyone and make announcement via our upcoming changes page. You can stay up to date about new features & releases with our Web SDK [upcoming changes](https://marketplace.zoom.us/docs/guides/getting-started/stay-up-to-date/upcoming-changes/web-sdk) and [change log](https://marketplace.zoom.us/docs/changelog) page.

1 - [https://marketplace.zoom.us/docs/sdk/native-sdks/web](https://marketplace.zoom.us/docs/sdk/native-sdks/web)  
2 - [https://forums.developer.apple.com/community/safari-and-web/html](https://forums.developer.apple.com/community/safari-and-web/html)  
3 - [https://www.mozilla.org/en-US/firefox/76.0/releasenotes/](https://www.mozilla.org/en-US/firefox/76.0/releasenotes/)

Thanks

---

<div class="post-metadata">

**Author:** ![cquibada](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/cquibada/32/13063_2.png) [@cquibada](https://devforum.zoom.us/u/cquibada)\
**Post date:** [June 2, 2020, 1:10am UTC](https://devforum.zoom.us/t/critical-no-audio-for-mobile-ios-browsers/19721/3 "2020-06-02T01:10:10Z")

</div>

Hi @michael_p.zoom,

Thanks for replying to my concern.  
Question, how long do you guys generally keep old versions usable? Is there a set amount of weeks/months until a version is deprecated? How long until 1.7.7 would be deprecated?

Thanks,  
Cary

---

<div class="post-metadata">

**Author:** ![ayzaedu.live](https://avatars.discourse-cdn.com/v4/letter/a/ba9def/32.png) [@ayzaedu.live](https://devforum.zoom.us/u/ayzaedu.live)\
**Post date:** [June 2, 2020, 8:21am UTC](https://devforum.zoom.us/t/critical-no-audio-for-mobile-ios-browsers/19721/4 "2020-06-02T08:21:59Z")

</div>

When we participate in the iphone 7 (ios) safari browser, we cannot connect to the sound. In other browsers, there is no screen. The only problem in the Safari browser is the sound problem …

 ![](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/2X/b/b9dd4fbe826bf83908c2acd34b79c04c42320ba2.jpeg)

---

<div class="post-metadata">

**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\
**Post date:** [June 2, 2020, 9:41am UTC](https://devforum.zoom.us/t/critical-no-audio-for-mobile-ios-browsers/19721/5 "2020-06-02T09:41:41Z")

</div>

Hi @ayzaedu.live,

Please see my comment above

> [@\[CRITICAL\] No Audio for mobile iOS browsers](https://devforum.zoom.us/t/critical-no-audio-for-mobile-ios-browsers/19721/2):
>
> Hi @cquibada, There is a limitation with using Computer Audio with iOS devices. Currently, Safari does not support the Audio worklet API which limits the use of Computer Audio for our WebSDK since we use Web Assembly instead of WebRTC[1]. For other browsers on iOS such as Chrome, Edge, or Firefox, they have to use the same engine on iOS which is why they work on Android but not iOS. Currently, we are waiting for Apple’s Safari to adopt the Audio worklet API for us to enable computer audio. Yo…

---

<div class="post-metadata">

**Author:** ![ayzaedu.live](https://avatars.discourse-cdn.com/v4/letter/a/ba9def/32.png) [@ayzaedu.live](https://devforum.zoom.us/u/ayzaedu.live)\
**Post date:** [June 8, 2020, 7:01am UTC](https://devforum.zoom.us/t/critical-no-audio-for-mobile-ios-browsers/19721/6 "2020-06-08T07:01:10Z")

</div>

We used the following library for the audio booklet, but we did not get any results. Could this be because the sound merge button on the computer is not visible? In other words, the button does not appear as seen in the picture, participation cannot be activated.

> **[GoogleChromeLabs/audioworklet-polyfill](https://github.com/GoogleChromeLabs/audioworklet-polyfill#why-are-worklets-emulated-on-the-main-thread)**
>
> 🔊 Polyfill AudioWorklet using the legacy ScriptProcessor API. - GoogleChromeLabs/audioworklet-polyfill

  
 ![](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/2X/b/b9dd4fbe826bf83908c2acd34b79c04c42320ba2.jpeg)

---

<div class="post-metadata">

**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\
**Post date:** [June 8, 2020, 4:09pm UTC](https://devforum.zoom.us/t/critical-no-audio-for-mobile-ios-browsers/19721/7 "2020-06-08T16:09:09Z")

</div>

@cquibada

> [@cquibada](#):
>
> Thanks for replying to my concern.  
> Question, how long do you guys generally keep old versions usable? Is there a set amount of weeks/months until a version is deprecated? How long until 1.7.7 would be deprecated?
> 
> Thanks,

We try to keep versions alive for several months to years, however with the new security fixes for the GCM encryption, we were forced to EOL older versions.

Hi @ayzaedu.live -

> [@\[CRITICAL\] No Audio for mobile iOS browsers](https://devforum.zoom.us/t/critical-no-audio-for-mobile-ios-browsers/19721/2):
>
> Hi @cquibada, There is a limitation with using Computer Audio with iOS devices. Currently, Safari does not support the Audio worklet API which limits the use of Computer Audio for our WebSDK since we use Web Assembly instead of WebRTC[1]. For other browsers on iOS such as Chrome, Edge, or Firefox, they have to use the same engine on iOS which is why they work on Android but not iOS. Currently, we are waiting for Apple’s Safari to adopt the Audio worklet API for us to enable computer audio. Yo…

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 9:55pm UTC](https://devforum.zoom.us/t/critical-no-audio-for-mobile-ios-browsers/19721/8 "2020-08-21T21:55:14Z")

</div>

Closed on August 21, 2020, 9:55pm UTC


