Beacon URLs undetectable
Reported by
pietrote...@gmail.com,
Dec 30 2016
|
||||
Issue descriptionDevice name: Google Nexus 5X Build/NMF26F From "Settings > About Chrome" Application version: 57.0.2965.0 Operating system: Android 7.1.1 URLs (if applicable): Steps to reproduce: (1) Settings > Privacy > Physical Web (Enable Physical Web) (2) Enable Bluetooth and GPS (if they aren't enabled) (3) Press Discovery button Expected result: Beacon URLs Actual result: Nothing
,
Jan 4 2017
If no beacons near by , you will see the message "No near by beacons"
,
Jan 4 2017
No, there is a Beacon. With Google Chrome I see the Beacon, bit with Chromium I don't see the Beacon. I tried with other devices but I get the same results (I don't see the Beacon with Chromium but I see It with Chrome or Physical Web app).
,
Jan 7 2017
Logcat show this:
cr_PhysicalWeb: Nearby connection failed: ConnectionResult{statusCode=UNKNOWN_ERROR_CODE(2802), resolution=PendingIntent{db21764: android.os.BinderProxy@34c9dcd}, message=null}
,
Mar 8 2017
,
Mar 8 2017
Apologies, but this is expected. At the moment only official builds of Chrome can scan for beacons because of the way we subscribe to Nearby. We are exploring ways to add a raw Bluetooth scanner to chromium which can be used in such cases. Sorry for the confusion! I've filed crbug.com/699586 where you can comment or track progress. |
||||
►
Sign in to add a comment |
||||
Comment 1 by pietrote...@gmail.com
, Dec 30 201661.9 KB
61.9 KB View Download