0

While Testing with ibeacons in background mode, i have found a big problem with detection using:

IN FOREGROUND WORKS FINE

func locationManager(_ manager: CLLocationManager, didRangeBeacons beacons: [CLBeacon], in region: CLBeaconRegion) {}

The idea I want to implement is to manage on my own the time a beacon can be detected a second time, keeping me close to the beacon.

The problem is when try to detect the same beacon for second time (and sometimes even others for first time), for some strange reason this funcion is not called anymore, just after first detection.

The only way is remove battery from beacon (intermittent) or take my beacon and walk Until leaving the detection area (This always works).

for this last i'm using this function for verify:

func locationManager(_ manager: CLLocationManager, didDetermineState state: CLRegionState, for region: CLRegion) {
    
    if (state == CLRegionState.inside)
    {
      print("didDetermineState inside!!!!")
    }
    else if (state == CLRegionState.outside)
    {
      print("didDetermineState outside!!!!")
    }
    else
    {
      print("didDetermineState Other!!!!")
    }
  }

Only executing some of this 2 option, the function is fired again

Thanks in advance.

UPDATE

Considering this answer, didRangeBeacons should be executed constantly, but i'm experimenting didEnterRegion issue.

I'm using both functions:

 - didRangeBeacons: for beacons visibles in ranging.
 - didEnterRegion: for Geofencing and beacons too
Community
  • 1
  • 1
jose920405
  • 7,982
  • 6
  • 45
  • 71

1 Answers1

2

Beacon ranging on iOS generally only works when your app is in the foreground. Ranging in the background is limited to 10 seconds after your app goes into the background. If you are also monitoring (which it sounds like you are), it also gets an extra 10 seconds of background ranging time whenever there is an entry/exit event -- e.g. if all beacons in the CLBeaconRegion stop being detected (exit) or after the first time one is detected (entry) after an exit event. This probably explains what you are seeing.

You can extend background ranging time up to 180 seconds by request, but you can only make it go on indefinitely with special background modes. I wrote a blog post that describes this in detail here.

davidgyoung
  • 63,876
  • 14
  • 121
  • 204
  • Thanks for the clarification, a very important point that I needed to clarify is that this error only happens in the background, in foreground works well – jose920405 May 31 '17 at 15:16
  • `extend background ranging time` is a good idea, but for now is not my principal problem. Considering this answer: https://stackoverflow.com/questions/26251076/difference-between-didenterregion-and-didrangebeacons#answer-26253473, `didRangeBeacons` should be executed constantly, but i'm experimenting `didEnterRegion` issue – jose920405 May 31 '17 at 16:04