Beacon Exits region and is unavailable for extended periods

Question

Created 1d

Replies 1

Boosts 0

Participants 2

Hi,

We are using beacon ranging methods to detect beacon in foreground and background in our app. We are using beacon's UUID, major and minor values to create a beacon region and then calling locationManager.startRangingBeacons to range beacons. We listen for beacon updates via the didRangeBeacons delegate method to get beacon data emitted.

However, we've observed some inconsistent behavior:

The beacon region frequently reports exit events even when the device is within close proximity (approximately 1.5 to 2 meters).
There are instances where no beacon updates are received for extended periods (up to 15–20 minutes), despite the beacon being nearby.

Generally, The distance between the device and the beacon is approximately 1.5 - 2 meters.

What could be the reason for this behaviour and how can we avoid it and continuously receive beacon updates when the beacon is near without any delay?

Thanks

Boost

Answer 1

Engineer OP

Apple

1d

First thing to check here would be to confirm that your beacons are fully compatible with the iBeacon specification.

We see that a lot of the beacons on the market are hybrid beacons supporting multiple technologies aside from iBeacon, and can be configured in various ways to support other methods of detection, and this can interfere with the region monitoring APIs from CoreLocation.

Especially for beacon ranging to work reliably, the beacons must comply fully with the specification and the payload must be calibrated according to the calibration steps in the specifications.

https://developer.apple.com/ibeacon/

0