@DarkMouse Are you using CKSyncEngine?

Thanks for confirming! I’ve filed a feedback report. My FB ID is FB19397537.

Yes, it is still not fix.

@donnywdavis Could you share what went wrong or how you fixed it? I’m having the same issue.

Interestingly, the Apple apps don't seem to exhibit this bug—I'm curious what they might be doing differently.

I noticed the same—no issues in Apple’s own apps like Safari or Mail. It might be related to UITraitCollection.current.userInterfaceStyle always returning .light. I also wonder if we’re missing something new for iOS 26, but since it worked fine in beta 2, it feels like a regression. I’d suggest filing a bug report—mine is: FB18871857.

How are you doing with iOS 15.3 Release Candidate 1 so far?

My bug report also changed from "Resolution: Potential fix identified" to "Open".

iOS 15.2 final did not fix the issue. :(

The status for my ticket went now from "Potential fix identified - for a future OS update" to "Open". Do you see the same? What is the current situation with iOS 15.2 beta 4 for you guys?

A lot of German news blogs as well, e.g.: Heise: https://www.heise.de/news/iOS-15-kann-Probleme-mit-Geofencing-bereiten-6275097.html Golem: https://www.golem.de/news/iphone-probleme-mit-lokalisierungsdiensten-unter-ios-15-2111-161323.html Electronic Research: https://www.electronic-research.de/ios-geofencing-problem.html Appgefahren: https://www.appgefahren.de/ios-15-mit-problemen-beim-geofencing-mehrere-apps-betroffen-311227.html

Still not fixed in iOS 15.2 beta 3. :(

The issue is still present in iOS 15.2 beta 2. My ticket now also shows the status: "Potential fix identified - for a future OS update".

For 3. "no events are delivered in the background (worst case)." I found an interesting workaround: If an affected user creates a custom Focus that is always on, allows calls for everyone and allows all apps (like a passthrough), the events arrive in the background again in the affected apps. This looks to me like a bug in the Focus engine of iOS 15. What do you think?

It would be interesting to know if this is now fixed in iOS 15.2 beta 2 or not.