Nearby beacons are not notified
Reported by
amruta.a...@gmail.com,
May 19 2016
|
||||
Issue descriptionSteps to reproduce the problem: 1. Enable bluetooth and Chrome flags related to Physical web 2. Keep a beacon near your phone 3. Wait for the beacon to show up as a notification What is the expected behavior? It is expected that the nearby beacons are notified as a notification on the phone/tablet. The beacons are only detected by only using an Android app which scans for beacons such as Physical Web or Beacon Scanner. What went wrong? No idea. Did this work before? N/A Chrome version: 50 Channel: n/a OS Version: Kitkat Flash Version: Shockwave Flash 22.0 r0
,
May 19 2016
,
May 20 2016
Sounds like this isn't a flag flipping issue and since it's KK, Chrome should already have the location permission -- I wonder if it's tied to the older version of Play Services
,
Jun 14 2016
Is there anything else that I can try from my side ?
,
Nov 14 2016
Closing since this is obsolete. We no longer intend to fire Notifications from Chrome.
,
Nov 15 2016
So is using the Physical Web app the only way to find beacons ? |
||||
►
Sign in to add a comment |
||||
Comment 1 by rsgav...@chromium.org
, May 19 2016Labels: triage-te