Can you provide a bit more information on how you're trying to intercept the redirect?  Is this by leveraging an extension API listening to requests and using native messaging?  Or through registering a custom protocol handler?  Or something else?

Comments from VMwware Identity Manager PM:

The launch from Workspace ONE to Horizon Client uses a custom URI scheme, ie:

URI: vmware-view://connection-server/desktop?SAMLart=XXXXXXXXXXXX 

BTW, as ARC++ / Android apps comes into the mix, my assumption is the above scheme may work with the Horizon Client for Android and Workspace ONE portal on Chromebooks, so the question is indeed how to handle ChromeOS apps launch appropriately.  Would love to know more from Google team (and if my ARC++ assumption is correct).

@4 Sorry, that doesn't quite clear up how they're trying to intercept calls to that URI.  Again, there are a number of different mechanisms they could use to try and intercept those calls, such as an extension API, registering a custom protocol handler, etc.  Whether this is a bug and how to investigate it depends very highly on those answers.

Adding some apps folks as well.

I reproduced the issue last night and my results were the same as the attached screenshot. I was using a more recent version of ChromeOS, the Horizon client, and vIDM than what I had 6+ months ago so I’m not surprised the result has changed. I don’t have a mechanism for deploying older versions of ChromeOS, the Horizon client, and vIDM so I’m no longer able to reproduce the “never-ending browser tab” result. 

Here are some of the technical details.

-	Chromebook model: Dell Chromebook 11 model CB1C13
-	Chrome OS version: 59.0.3071.134 (Official Build) (64-bit)
-	Chrome OS platform: 9460.73.0
-	Chrome OS firmware: Google_Wolf.4389.24.62
-	Chrome OS Blink: 537.36(@0)
-	Chrome OS V8: 5.9.211.41
-	VMware Identity Manager version: v2.9.1.0 Build 5594761
-	VMware Horizon Client for Chrome OS version: 4.5.0-5707752

This was done on an older Dell Chromebook that does NOT support Android apps. Meaning, I had to download the Horizon client from the Chrome Web Store, not via Google Play. So, I can’t say what the result would be for a newer Chromebook that supports Android apps. I can figure this out on Monday when an EUC colleague returns from National Guard duty. He has a new Chromebook we can use to test the Android result.

Per the bug notes, they’re waiting for us to tell them how we’re intercepting the URI. It sounds like we could use some direction from Google on which options exist on Chrome OS for this. It doesn’t seem that we’re explicitly intercepting the URI. Is this a correct assumption?

Should we setup a meeting to sync up with Google?

Deleted: Screen Shot 2017-07-27 at 9.47.10 AM.png 342 KB

	Screen Shot 2017-07-27 at 9.47.10 AM.png 342 KB View Download

-> rkc@ for apps/chromeos

And so we are all clear here is the expected behaviors today:

ChromeBook with Android App support:

Client launch option WORKS with Horizon for Android if it's installed
Client launch option DOES NOT work if only Horizon for ChromeOS is installed
This is the most recent screen shot previously attached to this bug.
 

Older ChromeBook:

Client launch launch option DOES NOT work if Horizon for ChromeOS is installed
Same as above
Browser launch is the only supported option
 

The fundamental question needs to be answered clearly is 'Can a web app in a browser instantiate a ChromeOS app via a custom URL scheme (which the ChromeOS app has registered)?'.  

In that context, the feedback I gave regarding how our integration works hopefully makes sense.  Meaning - intercepting the URL is not relevant.  This is an IdP initiated launch flow in the world of federated identity.

Happy to follow up with the Google eng team if they are willing. 

Hi Chromium team - any thoughts here about the launch behavior of a new ChromeOS app from another browser-based app? 

Bump. Any updates?

Customer is asking whether it is an actual bug or more a FR. Can you please update?

I'm unclear on how you're trying to launch the app, i.e. how the app registers the URL scheme.
Are you using https://developer.chrome.com/apps/manifest/url_handlers?

oh. yeah, afaik, url_handlers only support http and https, so I assume the answer is no 

Hi tbarzic@ , any news on this issue? please ping me if you need any additional information from customers.
  

Overall, it looks like it was never working before, but Vmware wants to register custom protocol e.g. "vmware-view" (for example via navigator.registerProtocolHandler) and then once there is a link e.g. vmware-view://horizonamer.vmtestdrive.com:443/ they want chrome to pass it to their extension (VMware Horizon Client for Chrome OS)

@Vmware is it like that?

Looks like feature request, since this functionality seems not to be there at this point.