Michael, please adjust priority or un-own as you see fit.

Well, this is definitely a bug, but probably not the one you intended to point out ;)

The android.intent.extra.VR_LAUNCH extra is only for deep linked apps, so it shouldn't let you enter VR at all. I think the problem here is we're not correctly handling 2D intents explicitly targeted at the VR Launcher. I'll have to investigate.

If you want to test out VR intents, the correct thing to do is send a normal 2D intent, but add the Daydream category to the intent. (com.google.intent.category.DAYDREAM or com.google.intent.category.CARDBOARD)

Note that Michael and I are chatting about #2 and will update the manual test plan accordingly. 

I'm going to dig into this some more, but it looks like your intent isn't the problem.

It looks like on Dev, the intents are going to CTA instead of CCT...

False alarm, Dev is fine. I had an unsigned dev build on.

On current Dev build I don't see the bug in the original post at all. With the VR Intents flag off I get taken to DD home. With the VR Intents flag on I enter VR as expected.

FYI, this will be fixed with https://bugs.chromium.org/p/chromium/issues/detail?id=821538

--ez android.intent.extra.VR_LAUNCH will no longer be required on VR intents (it'll be completely ignored, actually).

Any explicit intents to VrMainActivity will be treated as VR intents, and implicit intents (that don't specify the target activity) should resolve to VrMainActivity as long as they specify the cardboard category.