Chrome 49 on Android doesn't show detected Urls in the Physical Web view
See original GitHub issueI’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.
Is there some way I can debug this, or something I can reset to get it working?
Issue Analytics
- State:
- Created 8 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Chrome on Android doesn't show detected Urls in the Physical ...
Hello, I have "Beacon Scanner" android app for Eddystone beacon scanning, It working fine and have no problem of detecting UUID , TLM,...
Read more >Setting up Physical Web in Chrome - Google
Various mobile browsers are working to display these URLs. This document explains how to use the Physical Web on Chrome and Nearby Notifications....
Read more >Chrome DevTools Devices does not detect ... - Stack Overflow
To get the functionality up and running: Follow steps at https://developers.google.com/chrome-developer-tools/docs/remote-debugging; Install Windows USB ...
Read more >Chrome removes Physical Web support on iOS & Android
We noticed today that in the latest update of the Google Chrome app on iOS and Android support for the Physical Web has...
Read more >Suddenly, my Google search results are terrible. Chrome is up ...
A few days ago I started noticing that my Google search results are bad. After I search, the first results are tons of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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
@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 😉