New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 627750 link

Starred by 4 users
Status: WontFix
Owner: ----
Closed: Aug 2016
Cc:
ajha@chromium.org
niklase@chromium.org
█ kavvaru@chromium.org
█ brajkumar@chromium.org
dhadd...@chromium.org
songsuk@chromium.org
█ durga.behera@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Failed to start recording message is seen while recording using Screencastify/MediaCore capture extension in blaze device.

Project Member Reported by bj00129...@techmahindra.com, Jul 13 2016 
Version:54.0.2792.0/8581.0.0 (Official Build) dev-channel nyan_blaze
OS: Chrome-OS

Test urls:
1.https://chrome.google.com/webstore/detail/screencastify-screen-vide/mmeijimgabbpbgpdklnllpncmdofkcpn?utm_source=chrome-app-launcher-search
2.https://chrome.google.com/webstore/detail/mediacore-capture/enddmcjcfojolegmdogekfpfbobmkioo?utm_source=chrome-app-launcher-search

What steps will reproduce the problem?
(1)Signin to chrome>>Add any one of the extension mentioned above>>Now try recording and Observe.

Expected:Should be able to record desktop without any error message.
Actual: Instead Failed to start recording message is seen.

This is Regression issue as it is not seen in build-51.0.2704.37/8172.25.0 Beta Blaze

Note:
1.This issue is specific to Blaze device
2.Issue is not seen in today build M-54 54.0.2792.0/8581.0.0 dev channel Parrot, Paine
Actual_Screencastify.png
142 KB View Download

Comment 1 by brajkumar@chromium.org, Jul 13 2016

Cc: dhadd...@chromium.org songsuk@chromium.org
Labels: ReleaseBlock-Beta
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Chrome(Blaze) Version:54.0.2792.0/8581.0.0 dev by following steps provided in the above comment. Observed Screencastify app failed to start recording.

Comment 2 by sandeepk...@techmahindra.com, Jul 22 2016 

Issue is still able to reproduce in latest M54: 54.0.2800.2/8619.0.0-dev-channel- Jerry, Peach-pit as well

Comment 3 by asargent@chromium.org, Jul 22 2016

Cc: niklase@chromium.org
Components: -Platform>Extensions Blink>WebRTC
I don't think anything in the extensions system integration with webrtc code has changed recently, so this seems more likely to be a bug in webrtc code proper. Changing labels to see if someone from webrtc team can take a look.

Comment 4 by niklase@chromium.org, Jul 29 2016 

Can you check if https://chrome.google.com/webstore/detail/screen-recorder/gdamcnkmddbfhaadidkhahllkabienpk?hl=en also has a problem? That app is super simple and would facilitate debugging.

Comment 5 by jansson@chromium.org, Aug 9 2016

Labels: Needs-Feedback
[triage] bj00129141@ could you do the steps as suggested in #4 reproduces the issues you are seeing??

Comment 6 by bj00129...@techmahindra.com, Aug 10 2016

Labels: -Needs-Feedback
As per comment #4 checked with  https://chrome.google.com/webstore/detail/screen-recorder/gdamcnkmddbfhaadidkhahllkabienpk?hl=en  in latest build #54.0.2822.0/8687.0. Unable to reproduce the issue.

Also checked as per comment #0 in latest #54.0.2822.0/8687.0. Unable to reproduce the issue.

Comment 7 by jansson@chromium.org, Aug 10 2016

Labels: Needs-Feedback
bj00129141@ then the issue seems to be in the extensions themselves or they use the API in a way we do not and fails. Maybe we could reach out to them or file a bug on their site?

Comment 8 by jansson@chromium.org, Aug 31 2016

Status: WontFix (was: Untriaged)
Closing as per comment #6 and #7.
►

Sign in to add a comment