Open sstucchi opened 7 years ago
Does your URL pass in this validator? https://beaufortfrancois.github.io/sandbox/physical-web/url-validator/ If not, read these: http://blog.beeem.co/2016/03/top-4-things-to-watch-out-for-on-chrome-for-android-with-beacons/ https://www.beaconzone.co.uk/blog/troubleshooting-eddystone-url-on-android/
Yes it did, I tried before
You don't see beacons using Chrome at the moment. You need to turn on Settings>Google>Nearby. If you happen to have Bluetooth an location on, you should get a prompt to turn it on (but the settings is the way to make it happen)
Scott
On Tue, Feb 21, 2017 at 7:34 AM, sstucchi notifications@github.com wrote:
I am setting up a few beacons to broadcast URLs through Eddystone. I am using Estimote Location Beacons. iPhones and iPads receive the link and show it in the Chrome widget in the "Today" section. On the contrary, any Android device I tried so far does not receive the link through Chrome. The only way in which Android smartphones receive the link is through the Physical Web app. Is there a way I can make them work with Chrome? The link I am broadcasting is a HTTPS, and I set up the smartphones following these steps:
- Turn Bluetooth on: go to your home screen and tap Settings > Bluetooth> tap the slider
- Turn Location on: go to your home screen and tap Settings> Location> tap the slider
- Go to your home screen, tap Settings > Apps > Chrome > Permission and tap the slider next to Location
- Swipe down from the top of your screen, the link with the Physical Web icon should appear. IT DOES NOT
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/google/physical-web/issues/895, or mute the thread https://github.com/notifications/unsubscribe-auth/ABAbunimOCJYxdjyp28nvXXsbM8F-gzSks5rewPtgaJpZM4MHd-m .
THANK YOU!! It's working! Before I followed Google instructions about Android and the Physical Web https://support.google.com/chrome/answer/6239299?co=GENIE.Platform%3DAndroid&hl=en Apparently, they were wrong. Why is that? You told me exactly what I need to know, and you answered really quickly. Again, thank you Scott
Hi everyone, I'm involved in a Project that uses the EddyStone Protocol, but iOS devices or Androids with the App Physical Web easily receive the notifications, the problem occurs with the native Android Nearby that several times does not receive, I realized that any version 5.xx or 6.xx present the problem further. In all tests I have Location and Bluetooth enabled and Internet access. Is there any extra setting for the native Android Nearby to run as the Physical Web App?
I am setting up a few beacons to broadcast URLs through Eddystone. I am using Estimote Location Beacons. iPhones and iPads receive the link and show it in the Chrome widget in the "Today" section. On the contrary, any Android device I tried so far does not receive the link through Chrome. The only way in which Android smartphones receive the link is through the Physical Web app. Is there a way I can make them work with Chrome? The link I am broadcasting is a HTTPS, and I set up the smartphones following these steps: 1) Turn Bluetooth on: go to your home screen and tap Settings > Bluetooth> tap the slider 2) Turn Location on: go to your home screen and tap Settings> Location> tap the slider 3) Go to your home screen, tap Settings > Apps > Chrome > Permission and tap the slider next to Location 4) Swipe down from the top of your screen, the link with the Physical Web icon should appear. IT DOES NOT