Cannot setParameters on RTCRtpSender during a meeting

[boussadkh]

What happened and what did you expect to happen?

just reoppening the issue #2947 since i'm facing the same issue. Since the error is thrown by the Chime SDK, I can't confirm the exact cause, but I suspect it may be related to toggling the audio mute/unmute or the camera status

The error

Uncaught (in promise): InvalidStateError: Failed to execute 'setParameters' on 'RTCRtpSender': Failed to set parameters since getParameters() has never been called on this sender

here the code snippet if it can help

setMic(active: boolean) {
    if (!active || this.role === Role.ADMINISTRATOR) {
      this.audioVideo?.realtimeMuteLocalAudio();
    } else {
      // mute and unmute to reset the audio context
      this.audioVideo?.realtimeMuteLocalAudio();
      this.audioVideo?.realtimeUnmuteLocalAudio();
    }
    this._micActive = active;
  }

  toggleMic() {
    const newMicState = !this._micActive;
    this.storeInitialMicStatus(newMicState);
    this.setMic(newMicState);
    this.broadcastDeviceStatus(newMicState, InputDeviceType.MICROPHONE);
  }
```ts


### 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


create a meeting
Try to toggle mic with realtimeMuteLocalAudio() or realtimeUnmuteLocalAudio()
Try to toggle camera with startLocalVideoTile() or stopLocalVideoTile()
Send the value of the mic / camera with the realtimeSendDataMessage
The error appears randomly 


### Amazon Chime SDK for JavaScript version

3.22.0

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

chrome

### Browser version

123

### Meeting and Attendee ID Information.

_No response_

### Browser console logs

Uncaught (in promise): InvalidStateError: Failed to execute 'setParameters' on 'RTCRtpSender': Failed to set parameters since getParameters() has never been called on this sender

[hensmi-amazon]

If you are able to reproduce locally:

• Can you update to the latest JS SDK?
• Can you enable verbose console logs and provide those?

[boussadkh]

thanks for your answer
yes, i updated it. My logs are automatically sent to Sentry. What I noticed, if it can help, it seems that it's a method of RTPSender that is failing: third_party/webrtc/pc/rtp_sender.cc...
like
RTCError RTPSender::SetParameters(const RtpParameters& parameters) { if (!cached_parameters_) { return RTCError(RTCErrorType::INVALID_STATE, "GetParameters() must be called before SetParameters()."); } ... }

i'm not sure but after search i found that the only way to know that the RTPSender is ready is to observe the videoTileDidUpdate event 🙄

[hensmi-amazon]

Sorry i should have clarified, can you inject a logger to the Chime SDK so we can see the timings of our client changes? https://github.com/aws/amazon-chime-sdk-js/blob/main/guides/03_API_Overview.md#1a-create-a-logger you can use a console logger or forward to your current infrastructure.

What is the reproduction rate? Does it actually impact audio or video?

[boussadkh]

yes, I'm using a custom logger that implements Chime’s Logger interface.
I haven’t been able to reproduce the bug myself — it was reported by our client. When checking Sentry, I found at least 35 errors over the past few months.

From what I understand so far: the error is triggered by rtp_sender.cc.
Chime internally calls getParameters(), but sometimes the timing isn’t right relative to setParameters().

The solution — or at least a potential lead — would be to wait a short delay or to properly chain the calls after the RTCRtpSender is initialized.
This can be done by relying on videoTileDidUpdate.

Sample:

function waitForSenderReady(meetingSession) {
  return new Promise((resolve) => {
    const observer = {
      videoTileDidUpdate: (tileState) => {
        if (!tileState.localTile) return;

        // Local video tile ready => RTCRtpSender is probably ready
        meetingSession.audioVideo.removeObserver(observer);

        // Small safety delay (since getParameters() can be async internally)
        setTimeout(() => resolve(), 100);
      },
    };

    meetingSession.audioVideo.addObserver(observer);
  });
}

// after that we can chain calls
// example:
await meetingSession.audioVideo.start();
await waitForSenderReady(meetingSession);
meetingSession.audioVideo.setVideoMaxBandwidthKbps(600);

[hensmi-amazon]

Do you have any console logs besides the error? It's hard to hypothesize without a reproduction or more information.

Does this impact your application or is it just a benign error log?