Issue metadata
Sign in to add a comment
|
Chrome Andriod: "Failed to get access to local media. Error name was DevicesNotFoundError. Continuing without sending a stream" |
||||||||||||||||||||||
Issue descriptionChrome Version : 58.0.3007.3 / Dev / Chrome Canary 64-bit / Arm 64 Operating System : Android 7.1.1 Other browsers tested: N/A What steps will reproduce the problem? 1. Uninstall any previous Android Chrome Canary app 2. Install the Android Chrome Canary app (58.0.3007.3/canary): "adb -s Deviice_Id install android-canary-58.0.3007.3.apk 3. Allow Camera & Microphone for Chrome Canary in App settings: Settings > Apps > Chrome Canary > Permissions 4. Open the Chrome Canary App and open a new tab for a video only call https://appr.tc/?audio=false 5. Join a room 6. Another user repeats steps 1-5 and joins the same room What is the expected result? Verify that both sides can see each other (no audio). Make sure the call gets disconnected properly What happens instead? steps 5 & 6: Both users gets the error message: "Appr.tc says: Failed to get access to local media. Error name was DevicesNotFoundError. Continuing without sending a stream." Please provide any additional information below. Attach a screenshot if possible. The fault is NOT see observed whist doing an audio only call i.e replace step 4 with: https://appr.tc/?video=false The fault is seen on two diffent Android devices: Google Pixel XL Marlin (OS: Android 7.1.1) Samsung S6 (OS: Android 6.0.1) Note: The fault is NOT observed on Chrome Version: 58.0.3000.6 / Dev / Chrome Canary 64-bit / Arm 64 (Device: Google Pixel XL Marlin, Android 7.1.1)
,
Feb 13 2017
Can you try again with a later Canary? I believe this regression has been fixed.
,
Feb 14 2017
It seems 58.3012 with recent fixes works on other platforms, but not on Android. guidou@, please take a look. revision #450025 works on Android and #450026 doesn't.
,
Feb 14 2017
,
Feb 14 2017
I can reproduce the problem with versions 55, 57 and ToT between Android an Linux. I could not reproduce between Android ToT and Android Since I can reproduce with some combinations I'll try to fix the bug, but it looks more like an existing bug than a specific regression caused by #450026. Also, this is definitely not a P0. Lowering to P1.
,
Feb 14 2017
In #5 I meant I could not reproduce between Android ToT and Android 58.0.3011.0 (#449903)
,
Feb 14 2017
The repro I described in #5 was unrelated to this bug. I can reproduce fully on an Samsung S7 with ToT. Looking into it.
,
Feb 14 2017
,
Feb 14 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0725c8fd30b4076ecf805d4fab57a6eb4cc6e7f4 commit 0725c8fd30b4076ecf805d4fab57a6eb4cc6e7f4 Author: guidou <guidou@chromium.org> Date: Tue Feb 14 16:18:51 2017 Use fallback capabilities for devices that cannot list camera capabilities. The lack of the fallback made getUserMedia() fail on a number of devices. The fallback code already exists in media_stream_video_capturer_source.cc, but it will be removed from there once all the settings produced by the spec-compliant algorithm are used to configure video sources. Test CL: https://codereview.chromium.org/2692883004/ BUG= 691559 Review-Url: https://codereview.chromium.org/2694163004 Cr-Commit-Position: refs/heads/master@{#450373} [modify] https://crrev.com/0725c8fd30b4076ecf805d4fab57a6eb4cc6e7f4/content/browser/renderer_host/media/media_devices_dispatcher_host.cc
,
Feb 14 2017
revision #450373 should fix it. I tested it on a Samsung S7. jkallar@ / braveyao@, can you verify ?
,
Feb 14 2017
Verified with Chromium ToT #450395 on N5.
,
Feb 15 2017
,
Feb 17 2017
Verified Tested with Chromium 8.0.3014.0/canary on devices: Google Pixel XL (Marlin/Android 7.1.1) and Samsung S7 (Android 6,0.1)
,
Feb 20 2017
Issue 694136 has been merged into this issue.
,
Feb 22 2017
Spoke to guidou@ offline and he has written a CL that adds a test for this but the owners of the the files used in the tests are in the middle of a refactoring effort hence they told him to wait. Adding missingTests label to this so we can track of it. Hopefully the refactoring should be done soon.
,
Mar 14 2017
Re #15: sounds good. Is the refactoring possibly done now? Can we add a link to the CL here?
,
Mar 14 2017
The refactoring is done. Fixing the test CL to use it is in my queue. Expect it in the coming days.
,
Apr 10 2017
Re #17: Was the test CL landed or is it still in progress? Can you provide a link here?
,
Apr 10 2017
Still in the queue. I'll provide the link when available.
,
May 8 2017
Any update on the test CL?
,
May 8 2017
Still in queue, unfortunately. And it's a long queue.
,
May 15 2017
and what about now? ;)
,
Jun 6 2017
Even if it's a queue, having a bug that tracks that test makes sense, so we can help following up on it.
,
Jun 6 2017
Isn't this bug sort of open as long as it has the MissingTests label?
,
Jun 7 2017
FYI, I don't see this bug anymore in release/beta/dev Test page: https://3dthis.com/bugs/camera.htm
,
Jun 12 2017
re #24, I think it's more clear if we file a separate issue for the test and easier to track. The missingTests label is removed once a test or a separate issue has been filed for the test.
,
Jul 10 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by chfremer@chromium.org
, Feb 13 2017Owner: braveyao@chromium.org
Status: Assigned (was: Unconfirmed)