Both sites are working on ToT. I expect the breakages are due to the known bugs we're going to merge fixes back to M59 for.

Tried to dig into this a bit more.  There are some origin trial issues (tokens need to be updated), but with the WebVR flag enabled from chrome://flags the behavior is reproducible.

The android logs seem to imply the cpu can't keep up (some log lines follow, I'm not sure what are most important, but here is a sampling):
05-08 09:51:05.982   946  1983 I ActivityManager: START u0 {cmp=com.google.vr.vrcore/.daydream.DonPrepareActivity (has extras)} from uid 10077
05-08 09:51:05.989   946  1983 W ActivityManager: startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { flg=0x800000 cmp=com.google.vr.vrcore/.daydream.DonPrepareActivity (has extras) }
...
05-08 09:51:06.236  4057  4057 I GVR     : [vr/gvr/capi/src/gvr.cc:96] Initialized GVR version 1.42.0
...
05-08 09:51:06.243   946  1770 I ActivityManager: START u0 {cmp=com.google.vr.vrcore/.transition.TransitionViewActivity} from uid 10077
...
05-08 09:51:06.526   946  1034 I ActivityManager: Displayed com.google.vr.vrcore/.transition.TransitionViewActivity: +266ms (total +473ms)
...
05-08 09:51:06.550   946  1418 I WindowManager: Screen frozen for +290ms due to Window{aad5c75 u0 com.google.vr.vrcore/com.google.vr.vrcore.transition.TransitionViewActivity}
...
05-08 09:51:10.687   946  5196 I ActivityManager: START u0 {cmp=com.google.vr.vrcore/.daydream.MetaworldActivity (has extras)} from uid 10077
05-08 09:51:10.713   946   984 I VrManagerService: VR mode enabled
05-08 09:51:10.730  4057  4057 I GVR     : [vr/gvr/capi/src/gvr.cc:96] Initialized GVR version 1.42.0
...
05-08 09:51:11.746  4057 19773 W GVR     : [vr/gvr/render/scanline_racer.cc:1084] Missed vsync by 148470us (CPU load is too high)
...
...
05-08 09:51:52.265  4057 19773 W GVR     : [vr/gvr/render/scanline_racer.cc:1084] Missed vsync by 145968us (CPU load is too high)
...
05-08 09:51:52.385  4057 19773 W GVR     : [vr/gvr/render/scanline_racer.cc:1084] Missed vsync by 13349us (CPU load is too high)

Then it looks like GVR gives up and switch back (this is probably where it switches to the controller screen which is what I observed when getting these logs, all black might be slightly different):
05-08 09:51:52.524   946   946 I VrManagerService: VR mode disabled
05-08 09:51:52.540  4057  4057 I bvx     : Ui Overlay view reset
05-08 09:51:52.541  4057  4057 I ControllerService: Removing listener 10077:4057:com.google.vr.internal.controller.LISTENER_KEY for all controllers.
...
05-08 09:51:52.592  3918  3918 I Choreographer: Skipped 30 frames!  The application may be doing too much work on its main thread.
05-08 09:51:52.594   946   946 I VrManagerService: Leaving VR mode, disconnecting ComponentInfo{com.google.vr.vrcore/com.google.vr.vrcore.common.VrCoreListenerService} for user 0

@mthiesse, if those look like symptoms of the known bugs than we can probably mark this as a dupe of the existing bugs.

What are the issues with the tokens. Both are implemented for Spot the Bot. See attachment. 

Also seeing the same issue on https://konterball.com/ which also has both tokens. 

Deleted: Screen Shot 2017-05-08 at 8.17.38 AM.png 224 KB

	Screen Shot 2017-05-08 at 8.17.38 AM.png 224 KB View Download

There was a delay in getting the new tokens updating (even though a message went out saying they were ready to be updated).  This unfortunately meant that a lot sites requested new tokens for WebVR, but what they got were new tokens for the old trial (that isn't part of M 59).

The new tokens have a parenthetical in the data-feature name (if you copied it directly from the email), that looks like this (also see webvr.info/samples for an updated site example):
 <meta http-equiv="origin-trial" data-feature="WebVR (For Chrome M59+)" data-expires="2017-06-16"

Apologies for the confusion we may have caused in that regard.

Is this using beta version 59.0.3071.49?  That version was just released yesterday and should include most the known fixes (need to verify that though).

Ah, good news!
We tested on 59.03071.36. Will retest tomorrow with the exps that failed today's testing.

Tested all of the pre-existing experiments and here are the results. I've also included the I/O build of Spot the Bot. Is there timing on when fixes will be merged back into 59?


Spot the Bot I/O version: email schambers@ for link


The Musical Forest: https://forest.webvrexperiments.com/
     - Dev: Does Not Load
     - Beta: Does Not Load

Speak To Go: https://speaktogo.withgoogle.com/
     - Dev: WORKED
     - Beta: WORKED

Under Neon Lights: https://with.in/watch/under-neon-lights/
     - Dev:  "Not Compatible with Daydream headsets" 
     - Beta: Black Screen (this is weird because it works on stable)

Sonic Umbrella: https://sonicumbrella.com/
     - Dev: WORKED
     - Beta: Does Not Load

Mr Nom Nom: https://mrnmnm.com/
     - Dev:  WORKED
     - Beta: WORKED

Chromatic: https://chromatic.funktroniclabs.com/
     - Dev:  WORKED
     - Beta: WORKED

Finding Love: https://findinglove.activetheory.net/
     - Dev: "Not Compatible with Daydream headsets"
     - Beta: WORKED

Day & Night: https://dayandnight.moar.io/ 
     - Dev: "Not Compatible with Daydream headsets"
     - Beta: WORKED

Mass Migrations: https://massmigrations.com/
     - Dev:  WORKED
     - Beta:  WORKED

Bear 71: https://bear71vr.nfb.ca/
     - Dev: "Not Compatible with Daydream headsets"
     - Beta: Black Screen

When you re-test, you might want to disable WebVR in chrome://flags so you are also verifying that the sites are working correctly for end users. At least one of those sites did not have a valid token for origin trial (this should be resolved tomorrow). If you don't see the DON flow, it's not using the WebVR APIs and this should be flagged. For any such cases, you could go through them again with the flag enabled to check the implementation.

Version: 59.0.3071.49
OS: Android

Behavior:
- open Chrome beta version 59.0.3071.49 and go through flow
- get black screen and then am pushed back to the 'recentering DD page'

I looked at spot the bot and was able to repro the black screen issue in Beta 59.

I wasn't able to repro in canary 60.

The only difference I could see from the javascript logs was this line shows up when it works:
'World.requestPresent() finished with no errors'

I'm guessing that something is getting in the way of producing frames in 59 (hence a black screen) and after a timeout vr services reverts back to the DD page.

There shouldn't be major differences between 59 and 60, but more logs for the javascript calls might help in figuring out what is going on (or having someone  familiar with the code step through it in 59 to see where it fails).

Spot the Bot appears to be fixed by  issue 710863 , which will be merged to M59 today.

https://chromatic.funktroniclabs.com/ is not working in M59 or M60 contrary to comment 8, and it doesn't have an appropriate origin trial token ( issue 726406 ). Is this a site regression?

Will follow up right now to investigate. Thanks for flagging.

Chromatic should be working again for 59Beta. Haven't had a chance to check
60 but will do so this afternoon.

ticket can be closed. no longer an issue