iOS 27 Beta 3: iBeacon region monitoring sometimes never exits or enters

After upgrading to iOS 27 Beta 3, iBeacon region monitoring no longer behaves as it did on previous iOS versions.

Issue 1 – Never exits region

After connecting to an iBeacon, I power off the beacon and move several kilometers away. The app never receives an Outside (didExitRegion) event. Even after force quitting the app, powering off the beacon, locking the screen, and turning the screen back on, iOS may relaunch the app as if it were still inside the beacon region.

Is this an intentional change in iOS 27 or a bug?

Issue 2 – Sometimes never enters region

Occasionally, the app is not awakened when entering the iBeacon region. No Inside event is delivered. The only way to recover is to manually scan and reconnect to the beacon. Otherwise, the app is never awakened by the iBeacon again.

This worked reliably on iOS versions before iOS 27.

Issues popping like this in betas should immediately be reported as bugs so the teams can investigate and fix if necessary in a timely manner.

Please file a Bug Report on this

In your bug report we would need some diagnostics logs as well. Please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Bluetooth for iOS and Location services for iOS install the logging profiles on your device.

Then reproduce the issue, and follow the instructions at the above link to create a sysdiagnose.

And attach that to the bug report as well.

iOS 27 Beta 3: iBeacon region monitoring sometimes never exits or enters
 
 
Q