chrome update cause mic unavailable

[Ali Bahrami]

Suddenly, today the chrome browser updates itself to the newest version, 69, and the webrtc connection is lost.
There were no errors on version 67, but after update, I see this error (I'm using easyrtc and this is their error message):
Failed to get access to local media. Error code was NotFoundError.
I was thinking the problem maybe refers to easyrtc, not webrtc in generic form, but when I tested with test.webrtc.org I saw that the microphone is not on the list of devices it wants to allow permissions to use, and even the tests about the camera has been failed. Everything was perfect before update.

What should we do now?

Also, I do want to know is this because of my region (my beloved Iran) and is about regulations google applied to Iranian users, or this is a generic problem caused by update.

[Henrik Andreasson]

Platform, type of microphone, default sample rate?

Does the same happen with Chrome Canary?

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/91edfb02-f89d-48ff-916d-63604c0b74d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ali Bahrami]

Thanks for your reply

The problem is not platform specific, because I saw this on almost every platform (windows 7, ubuntu 18, android 4.4)

The problem is not microphone specific, as I said we have it working on chrome 67.

Yes, I've tested On version 70 beta, and the problem is there too.

With further investigation using DetectRTC plugin by MuazKhan, I found out that the browser cannot detect the microphone from top level. This means it is not recognizing there is a microphone out there. 

MuazKhan itself tested the version 69, and for him it is working fine.

I've attached the results of detectRTC plugin.

Thanks in advance

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAD2mqc6s%2BsC-WbLjx_8h7YP3HEBO4gaMTYwLOpiSRMPpsC1VpA%40mail.gmail.com.

[Henrik Andreasson]

Please file an issue here: https://bugs.chromium.org/p/chromium/issues/list

Add as many details as possible. Thanks.

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAFBa4fo6pm1sphpqG-1nmRpYGsMafF4DUm-QBQjU6hb_vOywCg%40mail.gmail.com.

[Ali Bahrami]

I will do it as you said.

Thanks

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAD2mqc6DDMJk3HvZQm520x6WdbB5VrBN1iM6Rry_hq7Dj%2B%2Bjsg%40mail.gmail.com.

[Lorenzo Miniero]

Ali,

can you share the issue address here when you open it? This may be related to a problem I've been experiencing myself (mic device with "Default" ID always failing) and so I'd like to keep track of that.

Thanks,

Lorenzo

[Henrik Andreasson]

Chrome Canary is version 71 and not 70. Please try it as well.

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/8a8d6d20-9ae8-48a6-accd-2235ab654d35%40googlegroups.com.

[Ali Bahrami]

I've checked Chrome Canary and the problem is stays there.

Thanks 

The link of issue is: https://bugs.chromium.org/p/chromium/issues/detail?id=891190

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAD2mqc5NjdPKK2_71i1d2EmP1y5AGkuSRqLThs1i6fA2v_Crng%40mail.gmail.com.