Google Stopping Support of Beacons on Nearby?

[chiphysler]

Google Stopping Support of Beacons on Nearby?

[ferencbrachmann]

I suggest you file a Nearby Bug Report here: https://github.com/google/physical-web/wiki/Taking-a-Nearby-Bug-Report

[chiphysler]

Thank you. It's my understanding that on March 1st Google changed something for anyone using Nearby.

[auge2u]

@chiphysler @ferencbrachmann
I have seen this as well. Looks like they are sunsetting the support in Nearby.
All the more reason for PW2 via PHWA.

For those that are not already involved, Join the slack channel here where we are upgrading the Physical Web standards and spearheading the initiatives for adoption, spam solutions, and commercial and public partnerships to implement PW2 as a ubiquitous solution for proximity engagement.

https://join.slack.com/t/physicalweb2/shared_invite/enQtMzMyMDYyMTE2NjE1LTA0NWRiNzdjYTM3NTFiODhjN2MxODMwMWM1NzhmZTE3YzRiZjA2ZTQyMTcxMGZkYzg3ODc3MWUwZDY5YWJjMDA

[firecast]

We had filed a bug report with Google Nearby engineers and they acknowledged the bug at their end and have since fixed it.

Thanks for the bug report, it helped us nail down an issue triggered in the presence of an invalid URL beacon (ex: a non-HTTPS page) in the proximity of other valid beacons. This bug was included in a software rollout last week, and the fix should already be live. Since the bug only manifested with multiple beacons, with one in an invalid configuration, the impact was likely limited.
This bug may have been triggered in your case because some of the content served on one of the beacons in the bug report used HTTP content (ex: an image served from an HTTP URL). Unfortunately all content must be HTTPS to be considered safe and to be served by Nearby Notifications. You can confirm everything is working correctly when you see a green lock in the Chrome address bar when visiting the page.
Thanks for your help, and we apologize for the disruption.