question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Using codec unsupported by the server causes uncaught error in promise

See original GitHub issue

Using v0.12.1 from nmpjs

  1. Use a server that does not have h264 as an enabled codec
  2. Create a video track with videoCodec: "h264"
  3. Note that the track is not published to the server, but no error or warning is spawned
  4. Mute the video track
  5. Unmute the video track, the following error is thrown in the console log:
01:51:47.553 LocalTrack.js?0f51:77 restarting track with constraints {width: {…}, height: {…}, frameRate: {…}, deviceId: {…}, resolution: {…}}
01:51:47.568 LocalVideoTrack {_events: {…}, _eventsCount: 2, _maxListeners: undefined, attachedElements: Array(1), isMuted: false, …}
01:51:48.257 LocalTrack.js?0f51:92 re-acquired MediaStreamTrack
01:51:48.258 LocalVideoTrack.js?646b:6 Uncaught (in promise) Error
Promise.then (async)
step @ LocalVideoTrack.js?646b:7
eval @ LocalVideoTrack.js?646b:8
__awaiter @ LocalVideoTrack.js?646b:4
restartTrack @ LocalVideoTrack.js?646b:163
unmute @ LocalVideoTrack.js?646b:71
(anonymous) @ VM22733:1

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
davidzhaocommented, Sep 15, 2021

oh interesting… I think we should keep it open for now. I was able to reproduce it with the same setup.

0reactions
bekriebelcommented, Sep 15, 2021

Thanks. Yeah, I noticed that mixing the codecs wasn’t working very well. I was also getting a lot of frame drops with h264, so I’ve just disabled it again for now. I updated the issue to reflect what is actually happening. Feel free to close if you consider it a non-issue, though.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Issues · livekit/client-sdk-js - GitHub
On devices with many media devices, some which are in use, loading media device ... Using codec unsupported by the server causes uncaught...
Read more >
Promise reject() causes "Uncaught (in promise)" warning
Answer: the reject in testReject is throwing to the Promise's implicit catch, at await testReject; and then throwing on to the .catch at ......
Read more >
How to Fix the Audio Codec Not Supported Error? - YouTube
In this video, we'll take a closer look at the “audio codec not supported ” problem. We have explained different methods that'll help...
Read more >
What are the common error messages to expect in Web ...
After integrating the Agora Web SDK into your web app, you can debug your code using the console log. This document lists the...
Read more >
MediaDevices.getUserMedia() - Web APIs | MDN
On browsers that support managing media permissions with Permissions Policy, this error is returned if Permissions Policy is not configured to ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found