Why Doesn’t Chrome Detect My Physical Web/Eddystone Beacon?

We have a lot of enquiries asking why Chrome on Android doesn’t pick up some beacons. This is often despite enabling the Physical web in Chrome.
Even mobiforge had problems.

The reason is almost always because the pointed to URL doesn’t use https. For some reason, probably as a defence against Man in the Middle attacks, Chrome on Android needs the URL to be secure otherwise it won’t be triggered. Note that the Android Physical Web app and also Chrome on iOS don’t have this limitation.

The fact that so many people are confused and it’s inconsistent with Chrome on iOS suggests that the Google hasn’t thought through or communicated this aspect well enough.

UPDATE: As of October 2017, Google removed Eddystone detection from Chrome on iOS and Android. Only Android can provide notifications.