URL advertised by advertise-url script linux not recognised by chrome

[vivekgalatage]

I tried to use eddystone-url/implementations/linux/advertise-url to check if the url can be seen in Chrome's privacy settings and nearby physical devices. But unfortunately the same can't be seen in the notification area or in the nearby physical pages.

But the same is visible if I install Physical Web app from the play store.

Any differences between chrome's behaviour and that of physical web app.

[scottjenson]

Unfortunately, many things can go wrong with code like that. The first thing you need to do is check to see if you are indeed broadcasting properly. The easiest way to do this is to install Nordic's excellent nRF Connect app. This will allow you to see ALL BLE devices and to make sure it's being broadcast at all. If so, check to see that it is marked with the Physical Web logo, confirming that it is indeed showing up properly. I've checked the code you referece and it does seem to be setting everything correctly (we had some old code previously and I wanted to make sure it hadn't stuck around) However, I can't test the code at the moment. If you can confirm you are indeed broadcasting a proper EddystoneURL frame then we'll move onto phase 2.

[PrabhanshuAttri]

Hi @vivekgalatage Try PyBeacon. It worked for nearby on android.

Installing PyBeacon

sudo pip install PyBeacon

[vivekgalatage]

With PyBeacon, I could see it in the nRF Connect

But chrome's Settings -> Privacy -> Physical Web -> Nearby is still not finding it.

Am I missing anything here?

PS: I am using chrome version: 51.0.2704.81

[scottjenson]

You're pointing to an HTTP page, Chrome/Nearby only shows HTTPS urls

[vivekgalatage]

I changed it to advertise https://www.google.com but still having the same issue.

[scottjenson]

So you're saying: 1) You're broadcasting "https://www.google.com" 2) You've confirmed by using the nrf connect app 3) You're not seeing it on your in Chrome or Nearby? (on the same phone?)

That's very very odd. You've got one BLE app showing the beacon is being received. Yet another can't. I don't know what to tell you. That's something I've never see before. If you're using Nearby, make sure you sleep/wake the phone. If you're using Chrome, tap the refresh icon.

[PrabhanshuAttri]

@vivekgalatage With PyBeacon, it works for me on Marshmellow.

Settings > Google > Nearby discoveries

Settings -> Privacy -> Physical Web -> Nearby

Try with default URL of PyBeacon (https://goo.gl/SkcDTN)

PyBeacon

If it doesn't work, then you could try installing all the updates. Just to let you know, I am also using the same version of chrome.

Hi @scottjenson does Physical Web app also shows https link? It's not showing estimote beacons with http urls.

[scottjenson]

only HTTPS urls are shown

[Nicknam3]

Hi,

I've the same problem, there is no notification and the nearby application (Web physical too) doesn't display my URL (with HTTPS). But i could see my beacon in the nRF Connect application or Beacon Toy.

Any idea ?

[scottjenson]

There have been a few updates to Google Play services. I'm checking in to see if things are improved. Remember, the first test is to open the Nearby Listview and refresh. If it doesn't show up there, you've got some type of HTTPS/robots.txt type of problem (e.g. we can't get to you)

Scott

On Fri, Feb 17, 2017 at 7:07 AM, Nicknam3 notifications@github.com wrote:

Hi,

I've the same problem, there is no notification and the nearby application (Web physical too) doesn't display my URL (with HTTPS). But i could see my beacon in the nRF Connect application or Beacon Toy.

Any idea ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/google/eddystone/issues/160#issuecomment-280674501, or mute the thread https://github.com/notifications/unsubscribe-auth/ABAbugAahHApPgG1JHU-YIDizG-6HvjCks5rdbevgaJpZM4JM_wl .