startAudio throwing Operation Timeout error in Firefox

Video SDK Web
1

hey @tommy and @vic.yang ,
While testing video call on Firefox, sometimes we have noticed an issue of startAudio API throwing Operation Timeout error as a result audio not getting joined.
We have a button where user can retry joining audio, but it always threw Operation Timeout error.

Although, we were not able to reproduce this error again, but just wanted to brought this up to know why could this happen?

Which Web Video SDK version?
1.3.0

Device:

  • Device: Macbook Pro
  • OS: macOS 11.6.1
  • Browser: Firefox
  • Browser Version : 101.0.1

Additional context

  • We have observed this issue only in Firefox.
  • We take both audio/video permissions using getUserMedia beforehand after Zoom’s join API is resolved.

Apart from this there is one more bug that we noticed regarding audio:

During the call If mic permission gets removed, audio gets disconnected, but current-audio-change doesn’t throw payload with action: leave, and also muteAudio/unmuteAudio methods resolves which I think should not ideally.

2

Hey @shoaib

Thanks for your feedback.

We will take a look at the audio issue in Firefox.
And you mentioned getting the microphone permission removed during the session, do you mean unplugging the microphone or disallowing the mic in the sysetem device manager?

Thanks
Vic

1 Like
3

hey @vic.yang ,

Thanks!

disallowing the mic in the system device manager.

4

Hello everyone,

we are also experiencing problems with the sound in firefox. The sound quality degrades suddenly after several minutes to the point that nobody can hear the speaker…
On Windows, SDK 1.2.7.

Thanks for having a look!

5

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

6

Hey @ol_mas ,

Can you try upgrading to version 1.4.0 to see if you are still experiencing the issue? Also, we would need to know steps to reproduce in regards to the SDK functions and any errors in the browser console to investigate further.

Thanks,
Tommy

7

Hey @shoaib , @ol_mas ,

Are you still experiencing this issue in 1.4.0+? We did include a fix in the 1.4.0 release.

Screen Shot 2022-09-16 at 10.32.39 AM

Thanks,
Tommy

2 Likes
8

Hey @shoaib , @ol_mas ,

Are you able to confirm my message above? :slight_smile:

-Tommy

1 Like