Beacon background monitoring

After a reboot, your app will not be alerted for iBeacon events until the user unlocks the device first. There is no way around this.

If you are having issues with iBeacon detection even after the user unlocks the device, barring any coding problems with your app, the first place to look at is the iBeacon advertising, and to make sure it is advertising 100% to the specs, and is also calibrated properly for its installed location.

I have a follow-up question for the same scenario:

Suppose the device was rebooted and the user did unlock it, but didn't get my app into the foreground (but some other app). I understand from your answer that in this case my app should get iBeacon detection events again, correct? Supposing that I set up everything correctly, of course.

Furthermore, two things come to mind in additon:

• First, it's possible that I "missed" a region update, e.g. a didEnter event occuring while the device was locked is basically "lost", correct? So I should probably verify in which region I am when I get the chance and not rely on the last region event to be enough of an indication
• Second, when exactly is my app really re-launched after the reboot? Before or after the unlock? I assume this happens after the unlock (once the first region update occurs)?

Yes, your app should get relaunched in the background - considering the beacons are advertising correctly, Bluetooth is turned on, etc. - without user interaction.

All this will happen only after the first unlock. Nothing will happen with your app after a reboot until after the first unlock.

Any events that happen before the first unlock can be considered lost to your app.

Thank you Gualtier, this helps me a lot.