Closed Bug 1824710 Opened 1 year ago Closed 1 year ago

Browserstack doesn't work in nightly

Categories

(Web Compatibility :: Site Reports, defect)

defect

Tracking

(firefox-esr102 unaffected, firefox111 unaffected, firefox112 unaffected, firefox113+ fixed)

RESOLVED FIXED
Tracking Status
firefox-esr102 --- unaffected
firefox111 --- unaffected
firefox112 --- unaffected
firefox113 + fixed

People

(Reporter: emilio, Assigned: denschub)

References

(Regression)

Details

(Keywords: regression, webcompat:site-wait)

[Tracking Requested - why for this release]: Browserstack is a common way for developers to test other browsers.

Bisected to: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=03dee83a03904f370c3539e78f3977ca6012ac4a&tochange=73fca811cf6ef5a9ed1ec3ac8c83b42e75366c38

STR:

  • With an account (I can help with that) go to https://live.browserstack.com
  • Select iPhone, and choose Safari, I was setting Safari 16 on iOS 14.

ER:

  • The emulator loads and I can test it.

AR:

  • Infinite waiting screen. This is on the console on the bad case:
Uncaught TypeError: attachMediaStream is not a function
    w https://d2ogrdw2mh0rsl.cloudfront.net/production/assets/newlive_livejs-d8a59b87cf.js:70
    init https://d2ogrdw2mh0rsl.cloudfront.net/production/assets/newlive_livejs-d8a59b87cf.js:70
    emit https://d2ogrdw2mh0rsl.cloudfront.net/production/assets/newlive_livejs-d8a59b87cf.js:65
    emit https://d2ogrdw2mh0rsl.cloudfront.net/production/assets/newlive_livejs-d8a59b87cf.js:65
    ontrack https://d2ogrdw2mh0rsl.cloudfront.net/production/assets/newlive_livejs-d8a59b87cf.js:67
newlive_livejs-d8a59b87cf.js:70:2911
    w https://d2ogrdw2mh0rsl.cloudfront.net/production/assets/newlive_livejs-d8a59b87cf.js:70
    init https://d2ogrdw2mh0rsl.cloudfront.net/production/assets/newlive_livejs-d8a59b87cf.js:70
    emit https://d2ogrdw2mh0rsl.cloudfront.net/production/assets/newlive_livejs-d8a59b87cf.js:65
    forEach self-hosted:203
    emit https://d2ogrdw2mh0rsl.cloudfront.net/production/assets/newlive_livejs-d8a59b87cf.js:65
    ontrack https://d2ogrdw2mh0rsl.cloudfront.net/production/assets/newlive_livejs-d8a59b87cf.js:67
    dispatchEvent resource://gre/modules/media/PeerConnection.jsm:820
    dispatchEvent resource://gre/modules/media/PeerConnection.jsm:1793
    fireTrackEvent resource://gre/modules/media/PeerConnection.jsm:1952
Flags: needinfo?(docfaraday)

Set release status flags based on info from the regressing bug 1510802

The JS console errors are not being helpful at all, since they indicate errors that have been invalid for a long time. However, I see mozRTCPeerConnection in their js code, seemingly being used for user-agent detection. That interface has been deprecated for nearly a decade, with console warnings, and we finally removed it in the regression range. This is very likely a site issue.

Flags: needinfo?(docfaraday)
Duplicate of this bug: 1824735

I poked David Burns, who should be able to help us get this looked at on their end.

I've verified that bug 1531812 is where this broke; this is definitely due to reliance on that mozRTC API.

Regressed by: 1531812
No longer regressed by: 1510802

I've also reached out via their support, and pointed them at this bug.

The following field has been copied from a duplicate bug:

Field Value Source
Regressed by bug 1804678 bug 1824735

For more information, please visit auto_nag documentation.

Regressed by: 1804678
No longer regressed by: 1804678
Severity: -- → S2

[Tracking Requested - why for this release]: correcting flag from prior edit.

Moving this over to the Web Compat product where I believe this should live. I guess we could potentially ship an intervention if we had to?

Component: WebRTC → Desktop
Product: Core → Web Compatibility
See Also: → 1823863

The bug is marked as tracked for firefox113 (nightly). We have limited time to fix this, the soft freeze is in 9 days. However, the bug still isn't assigned.

:denschub, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit auto_nag documentation.

Flags: needinfo?(dschubert)
Assignee: nobody → dschubert
Status: NEW → ASSIGNED
Flags: needinfo?(dschubert)

Changes have been made at BrowserStack, hopefully to be deployed in the next few days. Will update when deployed.

This has been deployed to BrowserStack prod.

Flags: needinfo?(dschubert)

Thank you all, BrowserStack is working again for me in Firefox Nightly.

Thanks for helping get this in front of the right people, David!

Closing as fixed. Thanks so much, David! <3

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Flags: needinfo?(dschubert)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.