Did enter in region local notification

BLE Beacons
1

Can you please explain me the actual flow for did enter in a beacon’s region of receiving local notification? I receive them with a considerable delay, and I wish I receive the notification instantly when I enter in a beacon’s region. Is there any solution or any explanation?
Thank you

2

It goes more or less like this:

  1. The user opens your app.
  2. You startMonitoring, which makes iOS note down that your app wants to be notified when the phone enters or exits range of a beacon that matches your CLBeaconRegion.
  3. The user then leaves your app or locks their phone.
  4. iOS puts your app to sleep. The app can’t execute any code at this time.
  5. Sometime later, when iOS detects the phone entered/exited range of a beacon, it’ll check what apps wanted to be notified of this event.
  6. iOS wakes up your app from sleep (or re-launches it from scratch, if the app got killed in the meantime).
  7. iOS delivers the didEnter/didExit event to your app.
  8. In your app’s didEnter handler, there’s code that tells iOS to immediately show a local notification.
  9. iOS shows the notification.

The delay usually happens in step 5, i.e., iOS detecting when you enter the range of the beacon.

If you have Location Beacons, you could try Estimote Monitoring, which is our attempt to make the beacon enter/exit detection more responsive and reliable:

3

Unfortunately, I have Proximity Beacons. Is there any solution for those ones?

4

Nothing that I know of, sadly :cry: You could open an “improvement request” on the Apple bug tracker, help us spread awareness about this problem with the Apple engineers: https://bugreport.apple.com/

We eventually hope to bring Estimote Monitoring to Proximity Beacons too, we’ve just decided to start small and focus really hard on a single hardware model to begin with.