Regarding significant locations, how long does it take for an iOS device to learn locations? We've done some testing and when we turned on stolen device protection and try to turn it off, it activated the security delay with significant locations on.

Why do I receive MKErrorDirectionsNotFound for transit directions even though the Maps app does provide transit directions for the same source/destination pair? Other transport types such as driving or walking return results just fine.

I'm facing a persistent location error on real iOS device: Error Domain=kCLErrorDomain Code=1 The operation couldn’t be completed. (kCLErrorDomain error 1.)

I have use cases where I want to specifically query against postal address and other properties that existed on CLPlacemark. With the new address type those are not exposed there. It might be contained in the text, so general string token searching is fine, but my data model saves postal code as an individually queryable component in my Swift Data model. FB16064707 FB20007974 FB20008112

It seems that with the latest update ellipsoidalAltitude of the CLLocation is always 0.0 where it had the correct value before. Also, velocity used to be -1 when not moving. The regular altitude still has sensible values. Did anybody else experience this ? Rgds Lob

I use location a lot in my app, and I've found that if the user moves far away (i.e. on vacation to a different country), the app shows a permission popup asking the user if they really want to keep location permission as always soon after. I've also found that providing some message from the app (i.e. in notifications) helps a lot more than what I can put on the permission popup to remind the user what this permission is used for, and helps my users make more informed decisions when they are asked about the location permission. Is there any best practices or heuristics I can use to decide when to show this notification? I just have some pretty simple logic in my app today, but would love to be able to provide a better experience.

Hi- I've never posted on here before! But ChatGPT hasn't been helpful with this. I have a call using MKLocalSearch (i have a waddled down version below) let region = MKCoordinateRegion( center: location, // the user's location span: MKCoordinateSpan( latitudeDelta: 0.005, longitudeDelta: 0.005 ) ) let req = MKLocalPointsOfInterestRequest(coordinateRegion: region) req.pointOfInterestFilter = MKPointOfInterestFilter(including: [.nightlife]) let search = MKLocalSearch(request: req) I made the latitude and longitude the lowest they can possibly be without throwing an error. Sometimes (and unreliably) when the user's location is at say, a bar, this list will give me like 10 bars that are not even within the region, and exclude the bar that the user is actually present in. How can i make this not the case? In other words, I just want this to return what I expect: a list of POIs with the category .nightLife within the defined region. Any help would be appreciated!

We have developed an iPad application using the ARCL (AR + CoreLocation) library to render Point of Interest (POI) annotations in both an AR view and a standard MapView. The application performs as expected on standard devices. However, we have some iPad covered with strong magnet. This creates significant magnetic interference, resulting in a 90° to 180° heading offset, rendering the AR POI placement and MapView orientation unusable. Technical Challenges & Constraints: Hardware Lock: The magnetic cover is a mandatory business requirement and cannot be removed during field use. Sensor Failure: The internal magnetometer cannot provide an accurate North reference due to the proximity of the cover’s magnets. While CoreLocation and CoreMotion use sensor fusion, the magnetometer remains the primary source for absolute heading. Alternative Orientation Tracking: Is there a documented method to bypass the magnetometer and derive device orientation using only the Gyroscope and Accelerometer (e.g., relative tracking) while still maintaining alignment with geographic coordinates in CoreLocation? Programmatic Offsets: Are there known APIs or mathematical workarounds to programmatically "nullify" or offset a constant magnetic bias once the device is inside the cover? so we can use that offset for ARView and in Mapview as well.

With iOS 26 deprecations around MKPlacemark, MKGeocodingRequest + MKMapItem is the migration path for forward geocoding. However, geocoding results don’t expose a canonical region/bounding region for the result set (similar to MKLocalSearch.Response.boundingRegion). Any idea how to mitigate this?

Hello, We are trying to understand the requirements for surfacing an action button on an Apple Maps place card for a POI. We created an Advanced App Clip Experience, associated it with a specific Maps location, and the location is marked as Matched. The experience status is green and marked Received. However, the main issue is that no action button appears on the Apple Maps place card for that POI. We do not see any button such as Order, Support, Reserve, Call, or any custom App Clip entry point. At this point, the issue is not only whether the App Clip launches correctly. The issue is that there is no visible Maps button for the user to tap in the first place. Could you please clarify: Does Matched + Received mean the App Clip is eligible to appear on the Maps place card, or does it only mean the association was accepted? What exact conditions must be met for an action button to appear on a POI in Apple Maps? Is button visibility controlled by the Advanced App Clip Experience configuration, the POI category, Apple Maps ranking/eligibility logic, Apple Business Connect, or a separate Maps partner integration? Are action buttons such as Order, Support, or Reserve available to standard Advanced App Clip Experiences, or only to approved Maps/Business Connect partners? If a business has authorized us to provide this experience for their listing, what is the correct process to make the action button visible on that POI? Is there any way to confirm whether a specific matched POI is eligible or ineligible for Maps place-card button surfacing? We want to understand the exact path from: Advanced App Clip Experience created → POI matched → status received → action button visible on Apple Maps place card. Right now we are stuck between “Received” in App Store Connect and no visible button in Maps, and the documentation does not clearly explain what gating step is missing. Related issue: FB23044674 (App Clip does not show up on Maps)

The Maps app exhibits a sophisticated blur effect behind the status bar: map content (labels, POI icons) is hidden map background (roads, buildings) is slightly blurred Can I achieve this effect in MKMapView, too? Just putting a UIVisualEffectView on top doesn't achieve the same effect since it also blurs the labels.

I am currently using Core location to get user's current location and few surrounding coordinates to draw annotations in Augmented reality. It works best on Cellular network and on Wifi network few times it is working ok and sometimes orientation is completely changed when device is connected to WiFi. Checked on Apple map as well, there itself it was giving wrong orientation and even after user is at same location, current location on map got fluctuating. On WiFi only models GPS accuracy is not good.

Hey everyone, in our project, the architecture sets all location services through one CLLocationManager, configured for navigation accuracy with background updates enabled. Start/stop is condition driven, so we track location while navigating, free-driving, connected to CarPlay or to a BLE device and stop immediately (no timeout) when none of those hold and the app is backgrounded. On stop() we tear down everything, including startMonitoringSignificantLocationChanges . BLE Device connection forces full background location for as long as it's paired and requires “Always authorization”. We keep one continuously-updating CLLocationManager (navigation accuracy, no distance filter, no auto pause) alive in the background whenever we're navigating, free-driving, connected to CarPlay, or to a BLE device using a CLBackgroundActivitySession on iOS 17+. Is a single always-best-accuracy manager the right approach, or should we be downgrading accuracy / using pausesLocationUpdatesAutomatically in some states for battery or performance? Any pitfalls with CLBackgroundActivitySession lifecycle we should watch for? As I wrote above, when the BLE accessory connects we force full background location on for the entire duration it's paired, and we require “Always authorization” for the BLE link to survive backgrounding. Is keeping location running the whole time an accessory is connected the right model? Thanks for the opportunity and have a great day!

Summary CLLocationSourceInformation.isSimulatedBySoftware (iOS 15+) fails to detect location spoofing when using third-party tools like LocaChange, despite Apple's documentation stating it should detect simulated locations. Environment iOS 18.0 (tested and confirmed) Physical device with Developer Mode enabled Third-party location spoofing tools (e.g., LocaChange etc.) Expected Behavior According to Apple's documentation, isSimulatedBySoftware should return true when: "if the system generated the location using on-device software simulation. " Actual Behavior Tested on iOS 18.0: When using LocaChange sourceInformation.isSimulatedBySoftware returns false This occurs even though the location is clearly being simulated. Steps to Reproduce Enable Developer Mode on iOS 18 device Connect device to Mac via USB Use LocaChange to spoof location to a different city/country In your app, request location updates and check CLLocation.sourceInformation?.isSimulatedBySoftware Observe that it returns false or sourceInformation is nil Compare with direct Xcode location simulation (Debug → Simulate Location) which correctly returns true

Summary While parallel testing Core Location on the new iOS 26.1 beta (23B5044i), I observed what I believe to be a regression of the issue described here: https://developer.apple.com/forums/thread/779192 Specifically, user positioning underground subway stations is noticeably inaccurate on the beta, whereas the same scenarios remain accurate on the unupgraded device below. I work with the MTA (New York City) and work with the OP of that thread. Happy to provide additional testing or details if helpful. Please let me know what else you need. Test Info Riding NYCT from Wall St to 34th St Penn Station on the 2 train carrying two iphones Recording: https://limewire.com/d/dpTWi#pDC3GRYIdE Expected: Consistent underground positioning comparable to prior releases. Actual: Degraded/inaccurate underground positioning on iOS 26.1 beta. Test Devices Left Screen: iPhone 15 Pro Max - iOS 26.1 beta (23B5044i) Right Screen: iPhone 11 - iOS 18.6.2 (22G100) Blue dots show location set by CoreLocation. Red dot on iphone 11 shows the actual location of both devices as I was able to manually place while travelling through a station. Placement through tunnels is not easy to verify and not usually indicated. Timestamps Comparison of when train was actually observed in a station vs when 26.1 and 18.6.2 CoreLocation updated to the station Fulton St 1:48 iOS 26.1 correctly updates (correctly) 2:16 iOS 18.6.2 updates (28sec late) Park Place 4:12 train arrives 4:15 iOS 18.6.2 updates to ~near Park Place 5:04 iOS 18.6.2 updates to Park Place (correctly) 6:07 iOS 26.1 update to ~near Park Place (over 2 mins late) Chambers St 6:02 train arrives / iOS 18.6.2 updates (correctly) 6:14 iOS 26.1 updates to ~near Chambers 6:18 iOS 26.1 update to Chambers (correctly) Franklin St 6:52 train arrives 6:55 iOS 18.6.2 updates (correctly) x:xx iOS 26.1 does not update Canal St: 7:16 train arrives 7:18 iOS 18.6.2 updates (correctly) x:xx iOS 26.1 does not update Houston St 7:54 train arrives 8:00 iOS 18.6.2 updates (correctly) x:xx iOS 26.1 does not update Christopher St 8:37 iOS 26.1 presumably between Houston St and Christopher St 8:40 train arrives / iOS 18.6.2 updates (correctly) x:xx iOS 26.1 does not update 14 St 9:22 train arrives 9:28 iOS 18.6.2 updates (correctly) 11:01 as train departs station iOS 26.1 updates (1.5 mins late)

I tried detecting fake locations using CLLocationSourceInformation.isSimulatedBySoftware, but it doesn’t work with spoofing tools like iTool AnyTo. It never gets flagged as simulated. Is this a limitation of the API, and is there any recommended way to detect virtual location tools on real devices?

When a business in Apple Maps has the wrong information such as address, postal code, there is a place to report an issue. After the issue is submitted, how long does it take to verify the new information and what steps are taken to check to see if it's accurate?

I am developing a navigation application. My goal is for this navigation app to also work in the background and provide the user with real-time directional updates. When apps request access to location services, users see a TCC (Transparency, Consent, and Control) prompt. This prompt allows the user to choose under what conditions the app can access location services (for example: “While Using the App”, “Always”, etc.). If the user selects the “While Using the App” option, can the navigation app still access location in the background and provide directional information to the user? Is something like this technically possible? Does Apple allow this behavior for navigation apps or similar use cases?

Hello, I'm working on an application that requires the use of significant location changes and visits, in addition to region monitoring and standard continuous location delivery (foreground and background). iOS 17 and iOS 18 introduced changes to how we can monitor distinct regions of interest (with CLMonitor) as well as receive location updates (with CLLocationUpdate). But I couldn't find any information regarding how to work with Significant location changes. Do we still need to create a location manager and call startMonitoringSignificantLocationChanges()? Where are the updates received in this case, in the locationManager(_:didUpdateLocations:) or in the liveUpdates async sequence? Visits. Same question here, for visit monitoring to work, do we still have to create a location manager then call startMonitoringVisits()? Where are the visits being notified? Still in locationManager(_:didVisit:) or in the liveUpdates asynchronous sequence? I just want to be sure I understand correctly how to use the updates, and if some features of Core Location still need to use a location manager and the delegate to receive the events. Maybe additional CLCondition will be added to cover both of these technologies as it seems highly related to monitoring conditions (significant location change, and visit). Thank you, Axel

Using Apple Maps, can we redirect employes to provider preferred vendors rather than what may be the most geographically logical choice? For instance, Healthcare providers are also employers. When provider employees have an urgent clinical need they use native tools to find care. They may ask, “Hey Siri, show me the nearest urgent clinic near me”. Apple maps plot a route to an urgent care but perhaps not the in-network, urgent care. Opportunity: Apple maps should know the device is an XYZ Provider corporate device and use a customer provided external table for routing to an in-network provider. The user may be directed two blocks north to an in-network provider vs two blocks east to an out of network, more expensive provider.