search

Estimote / iOS-Fleet-Management-SDK

Estimote Fleet Management SDK for iOS
https://developer.estimote.com
MIT License
1.18k stars 398 forks source link

Monitored Regions are Exited when they really weren't #259

Closed jackson13info closed 7 years ago

jackson13info commented 7 years ago

Currently I have the standard notification app example up and running. I post a local notification using UNNotificationCenter on iOS 10.3.2 when the iPhone device enters and exits a beacon's region.

The setup was fairly simple and pretty much emulates what the Estimote tutorial outlines. For some reason, when I watch the sample for a long enough time (5 mins) the delegate method beaconManager:(id)manager didExitRegion:(CLBeaconRegion *)region is called. This means that in a matter of minutes the didEnterRegion will also be called. Thus we are getting so many notifications even though the phone or beacon hasn't moved. At first I thought it may have been an issue with the beacon, but I have tried this same code with multiple different Estimote beacons.

Is this something that is expected to happen or a bug? If this is expected, is there any accepted workaround that people are using today? I assume that I may have to locally debounce the calls in a sense so that if you leave and then enter in a minute or two, that the leave didn't really happen.

Any help is definitely appreciated. Thanks in advance!

jackson13info commented 7 years ago

Looks like this is a common issue with Core Location.