Maybe release notes for 57 need to be updated if this is correct. 

Next time this happens, may you please also visit chrome://physical-web to show the list of nearby things?

There are times where we may not be able to find nearby beacons, such as if there is temporary trouble reaching the server, in which case it is expected that omnibox will not show results.

If the chrome://physical-web page has results and omnibox isn't showing content.

Also, just to confirm, this looks to be a DEV build of m57?  The Dev channel has omnibox support for 100% of users, but only after omnibox finch experiment settings have synced.  Beta is only 90%, and Stable is still at 0%.

Matt, is there any way we can confirm the state of the omnibox experiment?

(cut off sentence)  If the chrome://physical-web page has results and omnibox isn't showing content, then we should also confirm the omnibox experiment setting since physical web may sometimes he hiding suggestions on purpose.

+ Jason who had a long thread with Matt about the triggering criteria 

AFAIU, this might be WAI. Also, PW is not mentioned in the release notes for M57. 

Beacons nearby screenshot - https://drive.google.com/open?id=0B6GVWQnhaMClN0pmSzM0cGZnRG8

Working Build - 57.0.2972.0
Not working Build - 57.0.2975.0
Could not find the dev build in the console for - 57.0.2974.0

Update:
Not working from Build - 57.0.2975.0 dev

In Settings > Privacy, is there a "Physical Web" option underneath "Send Usage Data"?

If not, can you try force killing the app and restarting the app to see if it shows up?  
Thanks.

I'm unable to repro, I think this might be WAI.

1. Ensure Bluetooth is enabled and beacons are nearby.
2. Install Chrome from the Dogfood app.

The app only offers 58.0.3029.6, how can I install other Dev builds?

3. Check iOS Settings->Privacy

For some reason Chrome Dev doesn't show up here until I've launched it once. So, I did nothing here.

4. Launch Chrome (1st time), authorize Location when prompted.

Once Location is authorized the auto-enable conditions are met, but the auto-enable check won't be run until the next time Chrome is launched.

4a. Check that Physical Web preference is not visible in Chrome's privacy settings.

The Physical Web preference is behind a Finch flag which is disabled by default in the client but enabled for all users in Chrome Dev. For a fresh install, Finch config is synced the first time Chrome is launched and will take effect on the following launch.

At this point, because the Finch flag has not yet taken effect, the Physical Web preference should not be visible.

5. Force-quit Chrome, launch Chrome (2nd time)

This should trigger the auto-enable logic.

5a. Check that the Physical Web preference is visible and enabled in Chrome's Privacy settings.
5b. Check that tapping the omnibox displays a zero query result.
5c. Check that chrome://physical-web displays one or more nearby URLs.

I figured out what's going on.

vbhatsoori@'s build is 57.0.2987.100

Our Finch config for iOS Canary/Dev is in OmniboxBundledExperimentV1_iOSCanaryDev.json. This is a shared config for multiple Omnibox experiments to run in parallel without interfering with each other.

When we pushed to 100% on Canary/Dev we upped the min_version to 57.*.

This made room for new omnibox experiments to be added to the config. jdonnely@ added a new experiment Feb 23 and increased the min_version to 58.*. He also left our experiments enabled for all users.

After this change, our Finch config was no longer downloaded to 57.* builds on Chrome.

I think this should not be a launch blocker, since the latest Canary/Dev builds are 58.* and are unaffected.  Recommending resolving this as WontFix.

(Vinutha I returned your device to your desk.)

Thank you Matt.

Wow thats convoluted! Thanks for figuring that out.

mattreynolds@ is there any fix on the fly?

Resolving as WontFix, we're fine with leaving the feature off in 57.* Dev builds.