New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 803230 link

Starred by 2 users
Status: Fixed
Owner:
█ ymalik@chromium.org
(currently inactive on Chromium)
Closed: Mar 2018
Cc:
vsupruniuk@google.com
dougman@chromium.org
bsheedy@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression
Proj-XR
Proj-XR-VR



Sign in to add a comment

Re-entering ChromeVR via Intents fails

Project Member Reported by dbbrooks@chromium.org, Jan 17 2018 
Chrome Version:	65.0.3322.0
VrCore:	1.12.177372015
OS: Android N
Device: Pixel XL

What steps will reproduce the problem?
(1) Connect device via adb
(2) Open Daydream home app and enter VR
(3) run $adb shell am start -a android.intent.action.VIEW -n "com.chrome.dev/org.chromium.chrome.browser.vr.VrMainActivity" --ez android.intent.extra.VR_LAUNCH true -d www.google.com
(4) verify Chrome VR has started
(5) press the home button on the controller to return to Daydream home.
(6) run $adb shell am start -a android.intent.action.VIEW -n "com.chrome.dev/org.chromium.chrome.browser.vr.VrMainActivity" --ez android.intent.extra.VR_LAUNCH true -d www.google.com 

What is the expected result? Chrome VR should be started again.

What happens instead? After a brief black screen, the user remains in Daydream home.

Comment 1 by bsheedy@chromium.org, Jan 19 2018

Cc: bsheedy@chromium.org

Comment 2 by tiborg@chromium.org, Jan 22 2018

Labels: -Proj-VR-Shell Proj-VR M-66
Owner: ymalik@chromium.org
Status: Assigned (was: Untriaged)
Assigning to you, Yash, since it looks like a deep linking issue.

Comment 3 by ymalik@chromium.org, Mar 6 2018

Status: Fixed (was: Assigned)
This is not related to DLA but starting Chrome with a VR intent. This was fixed as part of https://chromium-review.googlesource.com/c/chromium/src/+/868913

I tested on Canary and seems to work.

Comment 4 by dougman@chromium.org, Mar 7 2018

Labels: Test-Complete
►

Sign in to add a comment