CLLocationManager didVisit no longer invoked reliably after iOS 26 updates

Question

Created 1w

Replies 3

Boosts 0

Participants 2

Since iOS 26 the delegate method locationManager(:didVisit:) is no longer invoked reliably while locationManager(:didUpdateLocations:) continues to be called regularly on the same devices. The issue appears to be directly tied to iOS version updates. Visit callbacks worked consistently under iOS 18.x but in some cases stopped being invoked immediately after updating the same device to iOS 26.0. In other cases didVisit worked on iOS 26.0 but stopped after updating to 26.0.1 and similarly from 26.0.1 to 26.1.

The behaviour is inconsistent with no identifiable pattern and affects multiple recent device models.

All required configuration is in place:

– startMonitoringVisits() is called correctly

– location permission is set to “Always”– background mode for location updates is enabled

– allowsBackgroundLocationUpdates is enabled

– restarting the app or the device does not fix the problem

The only workaround that restores visit monitoring is deleting the app and reinstalling the same App Store version which is not a viable solution for end users.

Have other developers experienced the same issue and are there any recommended best practices or technical guidelines to handle missing didVisit callbacks after updating to iOS 26?

Boost

Answer 1

Engineer OP

Apple

1w

This sounds like a regression our engineering teams need to investigate this issue, as this might indicate an issue with iOS 26.x

We'd greatly appreciate it if you could open a bug report, include any logs and sample code or models that reproduce the issue, and post the FB number here once you do.

We would also like a diagnostic log. It would be very helpful if you could please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Location Services for iOS to install a logging profile on your device. Then reproduce the issue, and follow the instructions at the above link to create a sysdiagnose. And attach that to the Feedback report as well.

Bug Reporting: How and Why? has tips on creating a successful bug report.

Important: For feedback related to a specific framework or API, select "Developer Technologies & SDKs" as your Topic, then select the specific technology and relevant OS. For feedback related to Xcode, App Store Connect, or other developer tools and resources, select "Developer Tools & Resources" as your Topic, then select the specific tool or resource.

0

Answer 2

effxbe OP

1w

Thank you for the response. I will file a Feedback report as suggested.

One complication is that the issue does not occur on my own devices. However I receive approximately 20–30 user reports per week with identical symptoms and my internal logging clearly confirms that locationManager(:didVisit:) stops being invoked entirely once the issue appears on a device. After that point no visit events are delivered anymore for that installation unless the user deletes the app and reinstalls it from the App Store.

Because the problem only affects end-user devices I currently do not have device-side system logs such as sysdiagnose or logs generated with the Location Services profile. I will still submit a Feedback with all information I have collected. If additional diagnostic data becomes available from affected users I will add it to the Feedback.

I will post the FB number here once it is created.

0

Answer 3

effxbe OP

1w

FB21022960

1