search

google / physical-web

The Physical Web: walk up and use anything
http://physical-web.org
Apache License 2.0
5.99k stars 665 forks source link

Chrome 49 on Android doesn't show detected Urls in the Physical Web view #613

Closed torbjornvatn closed 8 years ago

torbjornvatn commented 8 years ago

I've installed the new version of Chrome on my Nexus 5. Then I enabled the Physical Web setting in chrome://flags and the widget said it had detected a beacon, but when I clicked the widget the Physical Web view didn't show anything.

See this screenshot for a side by side comparison with the iOS version.

img_0098

Is there some way I can debug this, or something I can reset to get it working?

nondebug commented 8 years ago

Hi Torbjørn, thanks for bringing this to our attention. There's a known issue that can sometimes cause the URL list to be empty on first opening the activity. Sometimes refreshing works, sometimes you need to turn the screen off and on again to trigger a new scan. If that doesn't work, try force-quitting and reopening Chrome.

There's a fix in Chrome Dev that we believe addresses the issue you're seeing. If you have the time, could you install it and see if the beacon shows up reliably?

Starting in the current Chrome Dev build we've added a diagnostics page (chrome://physical-web) that can help determine why a detected URL isn't being displayed. Occasionally a beacon that was previously close enough to trigger the notification will be out of range by the time the activity is shown. On the diagnostics page, a URL in this situation is tagged "LOST". We also check that a URL can be resolved through the Physical Web service before we display it. If the URL is still nearby but can't be resolved, it's tagged "UNRESOLVED".

torbjornvatn commented 8 years ago

I actually got it working in "regular" Chrome, I had to change the URL broadcasted by the Eddystone beacon from our own site to facebook :confused:

So I guess that proxbook.com is stopped by the Physical-Web service somehow, because when I looked at chrome://physical-web in Chrome Dev it said UNRESOLVED. Is there any way I can find out why the service marks it as UNRESOLVED.

scottjenson commented 8 years ago

Does your website have a robots.txt file that specifies 'no crawl'? If so, we respect that directive

oahziur commented 8 years ago

Hi Torbjørn,

I think this is because your website has meta fragment redirects in the <head> section. The crawler we use does not follow the meta fragment and treat it as an error (to avoid meta fragment target url permanently redirects to the original url).

The temporary fix for the site is removing <meta name="fragment" content="!"> from the <head> section, but I will update this once I have more information on this.

Thanks, Rui

oahziur commented 8 years ago

@torbjornvatn A recent update on Physical Web Service should fix your site problem. Thanks.

torbjornvatn commented 8 years ago

Cool :sunglasses:

Chintanp038 commented 8 years ago

Hello sir,

I am testing on url send by eddystone beacons and it is detected by android phone by physical web in google chrome. it's working fine in iphone but struggling with the android phone.

I have: 1> Nexus 5X android phone with 6.0.1 version 2> updated google chrome with on physical web (on bluetooth and location)

Problem is that my device does not recognize the any URL and there is no such a option for "SEE NEARBY OBJECT " in Physical Web on page in my phone and also no getting any notification about the physical web

scottjenson commented 8 years ago

We should be rolled out to ALL android phones by end of the day (I know, this has been a confusing process for all, sorry about that but Chrome always rolls out big features slowly). Everything should be on by end of today. Other things to check:

On Fri, Mar 25, 2016 at 3:00 AM, Chintanp038 notifications@github.com wrote:

Hello sir,

I am testing on url send by eddystone beacons and it is detected by android phone by physical web in google chrome. it's working fine in iphone but struggling with the android phone.

I have: 1> Nexus 5X android phone with 6.0.1 version 2> updated google chrome with on physical web (on bluetooth and location)

Problem is that my device does not recognize the any URL and there is no such a option for "SEE NEARBY OBJECT " in Physical Web on page in my phone and also no getting any notification about the physical web

— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/google/physical-web/issues/613#issuecomment-201225494

koustubhavachat commented 8 years ago

Facing same issue , I am using HTTPS playstore link via google url shortner. Yesterday got following questions from client

  1. "When will user get notification if eddystone is broadcasting URL continously ? "
  2. "How can normal user will understand how to activate physical web using chrome ? "
  3. "Why can't google keep physical web ON by default in chrome ?"
  4. "How to implement security/authentication ? "
mrquincle commented 8 years ago

Is it still the case that HTTP cannot be RESOLVED?

ferencbrachmann commented 8 years ago

@mrquincle If the final destination URL is HTTP than it will not be resolved. If the forwarder is HTTP and the final destination is HTTPS than it will be resolved. As I'v suggested in Vienna, use a Beeem landing page for your beacons ;)

scottjenson commented 8 years ago

Agreed, the FINAL URL must be HTTPS for security reasons. Please use verify.physical-web.org to test any URL to make sure it works if you have any problems with a URL