search

google / eddystone

Specification for Eddystone, an open beacon format from Google
Apache License 2.0
3.08k stars 762 forks source link

Issue with non ".com" like ".io" #193

Closed stelliot closed 7 years ago

stelliot commented 7 years ago

Hi,

Eddystone-URL / Physical Web Issue

I have a problem with url's from domains like ".io" , ".se"... which isn't shown in Chrome. When I re-configure the beacon with a ".com" it works great.

I can see the broadcasted ".io" url's when using the "Beacon Tool" from Google but the links are not shown in Chrome Widget (iOS) or notification screen on Android.

scottjenson commented 7 years ago

have you tried putting your url into verify.physical-web.org? It's there to help debug situations like this.

Scott

On Thu, Nov 24, 2016 at 3:23 PM, stelliot notifications@github.com wrote:

Hi,

I have a problem with url's from domains like ".io" , ".se"... which isn't shown in Chrome. When I re-configure the beacon with a ".com" it works great.

I can see the broadcasted ".io" url's when using the "Beacon Tool" from Google but the links are not shown in Chrome Widget (iOS) or notification screen on Android.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/google/eddystone/issues/193, or mute the thread https://github.com/notifications/unsubscribe-auth/ABAbunJzdi8CD9zl3g5Ym6oZc1WeiyWxks5rBhyBgaJpZM4K8Ahv .

stelliot commented 7 years ago

Thanks Scott! It was the robots.txt file that was the issue. I'll guess this is for some sort of preventive security measure by Google that they want to have the pages pre-scanned before letting users access them.