Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Eddystone beacon not showing Nearby notification #948
After configuring a eddystone beacon I can see the "unregistered" Eddystone-URL in the Android "Beacon Tool" but not as "nearby notification".
I changed the URL and the ID if the beacon but it does not work. During my tests I figured out, there are request comming from the physical Web crawler:
`Every 2.0s: grep PhysicalWeb /var/log/apache2/ux5.de.access.log Ubuntu-1804-bionic-64-minimal: Sun Oct 7 13:42:42 2018
22.214.171.124 - - [07/Oct/2018:12:10:02 +0200] "GET /app HTTP/1.1" 301 2631 "-" "Mozilla/5.0 (Google-PhysicalWeb)"
My question is, why does the NearbyDiscovery repeats the message "Disabled by server https://ux5.de/game, https://play.google.com/store/apps/details?id=com.jentsch.smartsquares, URL invalid: https://play.google.com/store/apps/details?id=com.jentsch.smartsquares [CONTEXT service_id=49 ]"?
Links to the Google Play store are not supported:
Forgot to mention, you can send people to the app store using Eddystone UID rather than Eddystone URL. You need an Eddystone UID beacon, be sure to configure it with a unique ID numbers, then setup Google Beacon Dashboard account within Google's developer platform. It's a little tricky to figure out how to set it up the first time, but reasonably easy to handle once it is up and running.