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

Issue 646620 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

No access for apprtc calls on device Pit

Project Member Reported by srcv@chromium.org, Sep 13 2016

Issue description

Version: 54.0.2840.15 / 8743.23.0 dev
Device: Pit

What steps will reproduce the problem?
0. Start an apprtc loopback call using https://appr.tc/?debug=loopback
1. Open the javascript console (alt+cmd+j or ctr+shift+j) and watch for any errors
2. Listen for audio disruptions and watch for video stutter

Expected result:
a) AppRTC call should be established 
b) Local and remote audio/video should be clear 
c) There should be no javascript errors

Actual result:
a) AppRTC call successfully established 
b) Local and remote audio/video were clear 
c) But javascript console displayed following errors:
"https://collector.callstats.io/clockSync Failed to load resource: the server responded with a status of 426 (Upgrade Required)
987714888:1 XMLHttpRequest cannot load https://collector.callstats.io/clockSync. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://appr.tc' is therefore not allowed access. The response had HTTP status code 426."

Feedback submitted for this issue:
https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=user:srcv&lReport=21697253400

Notes:

This issue is observed only on device Pit and is also seen with apprtc peer2peer calls





 
Chrome_device_Pit_apprtc_loopback_webrtc_internals_dump_M54.txt
211 KB View Download
Labels: -Pri-2 Pri-1
Owner: jansson@chromium.org
Status: Assigned (was: Untriaged)
426 (Upgrade Required) sounds like an AppRTC issue, I don't see how that could be tied to the specific hardware? 
Did similar testing with another device work?

Comment 2 by srcv@chromium.org, Sep 14 2016

Yes. This issue is so far observed only on device Pit and not on any other chrome devices.
Filed https://github.com/webrtc/apprtc/issues/369 to show this to our callstats contact and he wrote they had issues in the backend yesterday which would be cause of this.

One take away here though is that apprtc should still work if callstats does not. Will file a bug for that.
Owner: srcv@chromium.org

Comment 5 by srcv@chromium.org, Sep 26 2016

Status: Verified (was: Assigned)
Tested apprtc calls (loopback and peer2peer) on chrome device Pit with M54 54.0.2840.39 / 8743.41.0 beta. Verified that apprtc calls are successfully connected and there are no javascript errors during the calls.

Closing this issue as verified.

Sign in to add a comment