Just curious if you got this working reliably? We have an app that needs to wake up when our iBeacons come into range and we’ve been noticing lately that while most users experience no issues, some users experience frequent failures where our app simply does not wake up even when the iBeacons repeatedly get brought into / out of range. it’s like iOS on their phone has decided our app is no longer going to be woken up until they bring the app into the foreground. Then everything works fine again for a few days - until it stops again. we just cannot figure out why most users have no issues while some have frequent issues. Why would iOS not launch our app in the background when a monitored beacon comes into range? When they get in this state we can bring the beacon in / out of range 10 times and nothing happens. But for days prior, even with the app killed by the user, it works fine.

Apple has just confirmed this to me that this is a known issue in iOS 15 and it should be fixed in iOS 15.1. We are experiencing the same issue, so fingers crossed.

Same here. Testing iOS 15.2 beta 3 and still the same issue. Given that this problem has apparently existed for 5 months it is quite troubling. So far what we have found is that if our app has been launched into the foreground recently (like in the last 24 hours or so), everything works as expected with region monitoring. However, if the user has not interacted with our app within the last day or so, all region events cease to function. On iOS 13 and 14 the exact same version of our app performed as expected. We could not launch the app for a month and region events would still function.