Environment: Tizen 9.0 In Mediasoup-client 3.6.58, I noticed it was using Bowser to detect the browser’s userAgent. And the mediasoup-client returns “Chrome74” for the device handler name. After updating mediasoup-client to 3.16.7, the library failed to load the device and returned an UnsupportedE…

The info from Bowser is wrong. Tizen is not based on Blink but on pure WebKit. And its User-Agent indicates WebKit 537.36. mediasoup-client requires WebKit >= 605. Support for older versions was dropped in Remove old handlers by ibc · Pull Request #331 · versatica/mediasoup-client · GitHub in media…

[image] Web Engine Specifications | Samsung Developer The world runs on you. Based on this, Tizen is using Chromium. If it is true, Tizen 9.0 is based on Chromium, will the problem be solved if I write: new Device({ handlerName: “Chrome111” }) ? Because I’…

Yup, I got wrong info. So assuming you mean the Samsung TV with Tizen 9, it is supposed to use Chromium M120 so mediasoup-client handler “Chrome111” should work. You say “can’t receive media” but I’m afraid I cannot assume that’s a problem in mediasoup-client. It could be something in your setup (in…

Alright. Will try that. [image] hasnarof: I have tried it, the Tizen can’t receive media. Sorry, I mean: device is loaded, Tizen can receive media, but can’t send media. Btw, is there any minimum mediasoup server version for mediasoup-client 3.15.0 ?

Please don’t ignore this: [image] Mediasoup-client can't load device in Tizen mediasoup libraries Without full debug logs is impossible to tell anything.

\par \cf0\highlight0 I/CHROMIUM( 6482): [INFO:CONSOLE: (1)] “%cmediasoup-client:Device %cdetectDeviceImpl() [userAgent:”%s", userAgentData:%o]%c +2ms color: #CC9933 color: inherit Mozilla/5.0 (SMART-TV; LINUX; Tizen 9.0) AppleWebKit/537.36 (KHTML, like Gecko) 120.0.6099.5/9.0 TV Safari/537.36 undefi…

I need all the logs with prefix “ mediasoup-client:Device”, not just the final one saying the result. [image] hasnarof: But, even though the userAgentData is undefined, it should work if I force it with new Device({ handlerName: “Chrome111” }) right? No, we don’t know. If there is no naviga…

Yes, I have tried using Chrome74, the device can be loaded, but Tizen can’t send media. Oh, and I forgot to tell you: Tizen: can send and receive audio/video camera. failed to send a share screen. can receive shared screen. Here are the logs from mediasoup-client and CHROMIUM-WEBRTC. In…

I’m afraid I don’t understand what your code is doing. I’ve cleaned up your logs and they make no sense: mediasoup-client:Device detectDeviceAsync() mediasoup-client:Device detectDeviceImpl() [userAgent:"Mozilla/5.0 (SMART-TV; LINUX; Tizen 9.0) AppleWebKit/537.36 (KHTML, like Gecko) 120.0.6099.5/9.…

Mediasoup-client can't load device in Tizen

mediasoup libraries

ibc (Iñaki Baz Castillo) October 17, 2025, 2:18pm 2

Without full debug logs is impossible to tell anything.

Topic		Replies	Views
Weird issue with Chrome/android and rtpcapabilities after device load mediasoup libraries	12	2127	September 20, 2020
Android native client support mediasoup libraries	81	8315	June 10, 2021
mediasoup-client not working on Firefox mediasoup libraries	14	2428	November 30, 2019
The latest mediasoup-demo don't work in newer chrome mediasoup-demo	0	303	November 19, 2022
mediasoup-client – Error Detecting Device with Chrome Extension mediasoup libraries	6	163	September 27, 2025

Mediasoup-client can't load device in Tizen

Related topics