Skip to main content
Question

Device not "exiting" iBeacon zone in JSS

  • July 29, 2016
  • 7 replies
  • 38 views

Forum|alt.badge.img+14

Has anyone else had trouble with devices constantly reporting they're in range of iBeacon zones in the JSS? I've been testing some beacons and I cannot get my devices to leave the area - even if I power the beacon off! In the inventory, the device shows it's still in all the previous iBeacon zones. I have attempted to run an updated inventory - which updates changed apps, not iBeacon zones.

I'm hoping for a more real time, in zone/exit zone, location tracking so we can apply specific policies based on (near) real time location.

Update - just found a device on an old test iBeacon that hasn't been powered on for over 4 months.

7 replies

Forum|alt.badge.img+3
  • New Contributor
  • January 23, 2017

I got the same problem...
the ipad do not leave the ibeacon region, even wiping the ipad does not force the ipad to leave the ibeacon


Forum|alt.badge.img+14
  • Author
  • Contributor
  • January 23, 2017

As best I can tell, this appear to be an issue in the JSS. We have devices that have been wiped and we have even removed some test beacons and they all still show up as in the zone. Perhaps the Self Service app isn't pulling iBeacon details correctly.


Forum|alt.badge.img+1
  • New Contributor
  • January 27, 2017

I have the same problem, devices are out of iBeacon zones and still showing up as registered with them in JSS inventory.


Forum|alt.badge.img+6
  • Contributor
  • March 7, 2017

I too have this issue and I just updated to JSS 9.97.1488392992. iPads do not exit regions even after ibeacon has been removed from jss.


Forum|alt.badge.img
  • New Contributor
  • August 10, 2017

Did anyone ever get a solution to this? The only way I can find to do it is to have another beacon overwrite the current. There should be an easier way...?


Forum|alt.badge.img+3
  • New Contributor
  • April 23, 2018

i got still the same problem, (2018)
Any solution right now?


Forum|alt.badge.img+2
  • New Contributor
  • January 30, 2019

I too am seeing this issue.