didEnterRegion and didExitRegion being called every minute

[_BMichael]

Hello everyone, I am new in beacons and I’ve read a tutorials(they’re great :)) for setting up, everything works fine, but then I get some glitch

I’ am using monitoring beacons in region (with UUID, major and minor values). The issue is, when I entered to region, after 2 minutes(approximately) calls a didExitRegion, but my beacon located in 20 inches from my device. Then calls didEnterRegion again and this happens periodically.
How can I prevent this case, does it exist some workaround to avoid this issue?

I just found the same topic (I guess author has the same issue) in stackoverflow, and there recommended to create a dictionary with date , but it didnt help me actually…

iBeacon enter and exit region constantly every 1 minute

How can I to detect the real exit/enter from the fake one ?

I’ll be glad to get your advises, thank you very much

P.S. Iam using the last SDK version, iOS 9.3.2, device is iPod Touch 6th generation.

[heypiotr]

Sadly, that’s a known problem with iOS:

Unreliable Region monitoring (false positives)

Hi! I’ve been working on a iOS app (quite simple) that monitors and range beacons. Ranging seems to be working ok, but I’m having some issues with the background beacon monitoring: My app currently is monitoring one specific beacon (Strong broadcasting power (4 dBm) & 1300ms interval). It simply sends a notification when didEnterRegion is fired, and another notification when didExitRegion is fired. The problem is that I’ve been having unreliable results with the background monitoring, where I…

There’s a possible workaround by @chaychoong here:

Workaround for unreliable beacon monitoring

Those using the Estimote Default packet type rather than iBeacon for the Proximity Beacons would have noticed that beacon monitoring is rather unreliable, often generating false positives. If you are facing the problem of didExitRegion and didEnterRegion triggering simultaneously every few minutes, you can use NSOperationQueue as a workaround. Ninja edit: code var operationQueue = NSOperationQueue() let beaconManager = ESTBeaconManager() func beaconManager(manager: AnyObject, didEnterRegion …

What this code does is, it delays the exit event by 3 seconds—if the exit was a “false” one, and is followed by an enter within these 3 seconds, it will discard the exit. You may want to play with the 3-second value.