yuweih: Is this yours?

It doesn't look like it is related to Chromoting..?

To clarify, there was a private email thread and danyao@chromium.org asked me to file this here.

danyao@ could you help me assign this bug to the right person?

Just tested on iOS 12 beta 5 and this issue is still present.

For what it's worth, I also installed a debugging-friendly browser called MIHtool on iOS, and it uses a webview and exhibits the same iOS 12-only issue. MIHtool allows me to view the javascript console, and I observed nothing particularly odd in the console output.

I think this will require some deeper digging on the part of a chromium developer and/or Apple developers.

+justincohen who can help take a look

Justin: please see crbug/868627 in Valetine for the test credentials.

juberti@ - would the WebRTC team be able to help take a look at this issue too? It looks like WebRTC works differently in WKWebView and Safari.

I was able to narrow things down significantly, and I even found a workaround for the issue so our app now works with all browsers.

There is still a question here, though. Please take a look at this jsfiddle:
http://jsfiddle.net/z5osdeg3/9/

If you run that script on various iOS and browser combinations, the output results are as follows:
iOS 11.4.1 with Safari:
ontrack: null
onaddstream: null

iOS 11.4.1 with Chrome 67.0.3396.87 (or any webview based browser like FF):
ontrack: null
onaddstream: null

12 beta 5 with Safari:
ontrack: null
onaddstream: null

iOS 12 beta 5 with Chrome 67.0.3396.87 (or any webview based browser like FF):
ontrack: null
onaddstream: undefined

In our app, we were depending upon the distinction between these results to know whether to add certain callbacks. I'm no longer depending upon it, so the app now works fine across platforms.

That said, why are the ontrack/onaddstream results on iOS 12 webview browsers different than safari on iOS 12?

-> rohit while justin is OOTO.

If it breaks in all webview-based browsers, then it's Apple's problem not Chrome's. Have you filed a radar for this? Lots of things behave differently between Safari and WKWebView, we just have to nag them when it happens. You can help by filing a radar at https://bugreport.apple.com. 

To be clear, the key difference is onaddstream being null in Chrome/iOS11 vs undefined in Chrome/iOS12?

FWIW, #14 behavior confirmed in local testing

Tracking rdar://43293240

> To be clear, the key difference is onaddstream being null in Chrome/iOS11 vs undefined in Chrome/iOS12?

Correct. It's not a huge deal at this point for us, but it'd be good to know the reason for this behavior difference between webview and safari.

andj2223@gmail.com: Are you still seeing this difference in iOS12 beta 12?

andj2223@gmail.com: Are you still seeing this difference in iOS12 GM?