+Elijah, +Sweet

Any idea why redirection is working in an Android browser but not on native Chrome? We've seen issues with this with WebEx meeting links as well. It's a very frustrating experience to users.

this should have been fixed ~year ago (b/27844371).  Is this a regression with the new intent picker or something?

I've had another customer report this issue for their users. If they use an extension to change the UA to Android, the redirection to the Skype for Business app works. I have test credentials to help with testing if needed.

I have been taking a look into this, the bug referred in comment#3 is not for this scenario, I Am also testing in M62 and I see the same behavior as today, so this is not a regression due to the intent picker redesign.

So far I can see that this dialog is shown since arc_external_protocol_dialog fails to find an intent-filter like "lync15:confjoin?url=httpssomething", Chrome OS has been capable of handling external protocols/schemes for a while, but somehow a filter for this scheme is not exposed.

Working on it.

+Sunil as per our convo

Team,

Any update on this? Had a another customer report this issue to me as well.

as described offline, we believe that the web property is blocking the redirection back to the app because Desktop Chrome does not present as an Android device.  A workaround (unless/until the web property is fixed) is to change your user agent to look like and Android browser.

Can you please explain why we are not going to fix this?
This is blocking enterprise customers from deploying Chrome OS.

I'm inclined to think this affects the Skype for Business experience on Chrome OS for Enterprise customers and we probably should not dismiss it.


kaned - can you provide a sense of how important this is to Enterprise? how many deals / units might this block? any big names that have highlighted this?

Can I add to this too? - This is blocking Enterprise customers from adopting Chrome OS. Interally we're a Google House but occassionally have to communicate with the outside world who haven't moved to Google (yet). 

I'll probably get laughed at if I ask my users to install an Android browser on their Chromebooks, especially Firefox. 

Skype meeting link from customer email opened chrome browser page showing Lync landing page with pop-up error saying "Google Chrome OS can't open this page".

If I right click the skype link (in email) and select to use Android Chrome Beta browser, this will start Skype for Business android app and sometime allows me to join the meeting, other times it does nothing (can't join).

Will solution be more native and not have dependency on android chrome browser?

The issue of redirecting url links from chrome to an android app has come up a number of times.

Elijah / Sweet - Is anyone on the platform team looking into this or anything similar? Skype for Business is an important enterprise app.

Sunil, what eng is saying is that Skype is detecting the Chrome OS user agent and is not even issuing the appropriate redirect. There's literally no chrome-os side fix we can make here.

Workaround would probably be to have an extension that changes the user agent to pretend to be an Android browser for specific urls (like meet.deloitte.co.uk/*) - there are lots of extensions on the webstore that can do this, such as https://chrome.google.com/webstore/detail/user-agent-switcher-and-m/bhchdcejhohfmigjafbampogmaanbfkg?hl=en. Not sure if they are configurable via policy, though, so some custom eng work might be required.

So, if you install this extension and change the user agent to look like android, do skype links work? 

I think chromium accounts have been stopped giving out, hence bouncing to Huan.

@Sunil, Drew described a potential solution and we need to gauge what

Finishing comment #17, 

@Sunil, Drew described a potential solution and we need your advice on what is an acceptable solution. Please setup a meeting if we want to talk through solutions, but we need to all get on the same page of the tradeoffs of possible solutions. 

shihuis@ - I had a meeting with huanr@ about this and we aligned on assigning this to him to resolve.

I've also created a doc here to track: https://docs.google.com/document/d/12RHniXriOYf_wH-zdw5KVrzcnDXWXPflUJj-z5GfV2Q/edit

Let me know if you have any qns / concerns. We can meet to discuss as well. Feel free to comment in the doc too.

Thanks Sunil for expanding, in that case, gladly handing back over to Huan to resolve :)