aws / aws/amazon-chime-sdk-js

Buzzing sound for ios and mac

Open
#3,003 1 comment 0 reactions 0 assignees View on GitHub
Browser Bug
Dominant language
TypeScript
Stars
761
Forks
474
Avg merge
3d 13h
Merged PRs (30d)
1

Description

### What happened and what did you expect to happen?

Running `DefaultMeetingReadinessChecker`'s `checkAudioOutput` on ios (safari/chrome)/ipados (safari/chrome)/mac (safari)/webkit based browsers causes tone to play infinitely. After resolving the `audioOutputVerificationCallback` the tone should stop playing, but on the above browsers/os combinations it continues to play.

I also noticed a closed ticket with a similar issue: https://github.com/aws/amazon-chime-sdk-js/issues/1515

### Have you reviewed our existing documentation?

- [X] GitHub [issues](https://github.com/aws/amazon-chime-sdk-js/issues)
- [X] FAQs [page](https://aws.github.io/amazon-chime-sdk-js/modules/faqs.html)
- [X] README [page](https://github.com/aws/amazon-chime-sdk-js#amazon-chime-sdk-for-javascript)
- [X] Feature-specific [guides](https://github.com/aws/amazon-chime-sdk-js#guides)

### Reproduction steps

Instantiate DefaultMeetingReadinessChecker
Run await DefaultMeetingReadinessChecker.checkAudioOutput
Resolve the callback with a button click
Notice Audio Tone continues to play even though checkAudioOutput has finished executing

### Amazon Chime SDK for JavaScript version

3.20

### What browsers are you seeing the problem on?

webkit based browsers (ios - safari/chrome, ipadOS - safari/chrome, macos safari)

### Browser version

ios-safari 18.1, ios-chrome-131.0.6778.73, ipados-safari 18.1, ipados-chrome-131.0.6778.73, mac-safari-17.5(19618.2.12.11.6)

### Meeting and Attendee ID Information.

_No response_

### Browser console logs

No logs are output from checkAudioOutput.

Contributor guide

Open the contributing guide

Research direction

Start at DefaultMeetingReadinessChecker.checkAudioOutput and reproduce the issue on the listed iOS, iPadOS, and macOS WebKit-based browsers. Review the related issue #1515 for context, then trace what happens after audioOutputVerificationCallback resolves. Done means the tone stops when checkAudioOutput finishes on all reported browser and OS combinations.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
audio-video-rtc
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.