Maps & Location

RSS for tag

Learn how to integrate MapKit and Core Location to unlock the power of location-based features in your app.

Maps & Location Documentation

Posts under Maps & Location subtopic

Post

Replies

Boosts

Views

Activity

MKMapItem addressRepresentations fullAddress singleLine does not always work and provides the address in multiline
Hello, I’m trying to display in my app the full address of an MKMapItem in a single line. I notice the following function does not always return single line but contains newlines. https://developer.apple.com/documentation/mapkit/mkaddressrepresentations/fulladdress(includingregion:singleline:) I provide the list of some identifiers so you can check what’s wrong. "I39866265D4A8562A", // 🟢 works "IF233A1E949A5566C", // 🟢 works "ICA31B6B98E02A528", // 🔴 does not work "ICA31B6B98E02A528", // 🔴 does not work "I9E00A04BFCB9718D", // 🔴 does not work "IFACDC4BC25712413", // 🔴 does not work "I74135A4F7C7FE654", // 🔴 does not work "IFE4A3BC4FEFA53E0", // 🔴 does not work You can check this FB25681688 Thank you, Regards, Axel
0
0
4
39m
[iOS 27.2.1 / iPhone 17 Pro] BLE Central app sporadically fails to detect region and interact with Peripheral
Hello everyone, I am developing a BLE-based room entry/exit authentication app and we are currently experiencing an intermittent issue where the app fails to respond to the reader. I am looking for any similar reports or potential workarounds. [Environment] Devices affected: iPhone 17 Pro (majority of user reports), iPhone Air (reproduced once internally) OS Version: iOS 27.2.1 [App Architecture] iOS App: Central Reader (Hardware): Peripheral [Issue Description] On the specific devices mentioned above, the reader and the iOS app sporadically fail to interact with each other. This unresponsiveness occurs at a frequency of approximately 1 out of 5 attempts. [Investigation Details] Our development team was able to reproduce this exact issue once on an iPhone Air. When analyzing the logs and behavior during this reproduction, we confirmed that although the device was physically well within the BLE region (range), the OS completely failed to detect that it was inside the region. [Questions] Is this a known bug regarding CoreBluetooth / CoreLocation region monitoring specific to iOS 27.2.1 or newer devices like the iPhone 17 Pro? If anyone has experienced this intermittent region detection failure on recent OS/device combinations, are there any known workarounds to force the detection or prevent the drops? Any insights or advice would be greatly appreciated. Thank you!
0
0
78
2d
Can’t submit IMDF! Approved for Indoor Maps Program, no upload path in ABR.
Has anyone recently found a working path to claim a venue and upload an IMDF in Apple Business Register? Our Locations page shows 0 locations with no option to add one. (Screenshot attached.) Our business is approved for the Indoor Maps Program, our location is approved/verified in Apple Business Register, and our IMDF file is complete and ready to submit. We just can’t find anywhere to submit it. The 2019 WWDC session “Introducing the Indoor Maps Program” shows a “Claim your location” flow and a per-venue upload dashboard that simply doesn’t exist in our account today. We emailed maps-indoor-support@apple.com on August 25 with no response. A few other threads here describe the same thing, IMDF or venue registration stuck with no visible next step, so this doesn’t look isolated to our account. Any pointers on where this actually happens now would help. This has been open almost three months with a completed file and nowhere to send it. I am trying to develop my app but cannot proceed without this piece.
0
0
45
2d
MapKit JS token returns 401 only for mainland China while Apple's official sample works
Hello Apple engineers, Feedback Assistant report: FB25612837 (submitted under our developer team). We are investigating a production Web MapKit JS authorization failure. Our native iOS App works normally; this report concerns Web MapKit JS only. Observed on 14 November 2026: Our portal-generated MapKit JS token returned HTTP 401 for mainland-China bootstrap authorization and HTTP 200 for US authorization. Apple's official embedded-map example worked in the same browser and network, returning countryCode CN and displaying Amap attribution. A minimal page using SDK 6.1.205 on our production Web domain also returned 401. SDK 5.81.72 had the same result. Exact-domain, wildcard-domain, expiring, and temporarily unrestricted diagnostic tokens produced the same China-only failure. The unrestricted token was revoked immediately after the test and was never deployed. Rechecked on 17 November 2026: The locally configured production token, whose hash matches the token inspected in production on 14 November, still returns HTTP 401 with {"error":{"message":"Not Authorized","details":[]}}. It uses ES256, scope mapkit_js, and an origin matching our Web domain pattern. It is not expired and has no duplicate header or payload claims. Separately configured root-domain MapKit JS tokens also return 401 when tested with their matching origin. These 17 November probes used locally configured tokens; the authenticated production token value was not freshly read back that day. We found matching reports: https://developer.apple.com/forums/thread/766180 https://developer.apple.com/forums/thread/748764 https://developer.apple.com/forums/thread/684701 We checked the duplicate-claims fix described here and ruled it out for our configured token: https://developer.apple.com/forums/thread/113670 Questions: Is any additional team provisioning or authorization required for the mainland-China MapKit JS service? Can regional validation treat portal-generated tokens differently, despite the same token being accepted by another region? Is there a supported corrective configuration we can apply? We have not found one in the current Maps token documentation. Developer Support case 30000015236904 directed us to the forums. We can provide account-specific details privately through Feedback Assistant. This public question intentionally omits tokens, private keys, account identifiers, customer data, and production logs.
0
0
51
4d
MapKit route animation exported to MP4: permitted use and appropriate Apple contact
Hello, I am Rabia, publisher of RotaTakip, a pre-launch iOS outdoor GPS app being developed with my son. We are evaluating Apple Maps for a user-initiated route-video feature and would appreciate a reference to official guidance or the appropriate Apple contact before enabling it. Proposed use: A user selects their own recorded GPS route and creates a short animated recap over an Apple map. The app saves an MP4 to Photos, and the user may share it on social media or play it on non-Apple devices. Rendering would happen on the user's device using public APIs. Required Apple and third-party attribution would remain visible. We would not extract raw tiles, scrape map data, build a map database, or perform bulk/server-side rendering. The app is planned as a paid, one-time-purchase GPS app. The map would be a main visual element in the exported recap. Video export remains disabled pending clarification. We are considering two approaches separately: MKMapSnapshotter images with our own route overlays, potentially a sequence of camera views, encoded with AVFoundation. A user-initiated ReplayKit recording of an animated MKMapView, with the required system consent and recording indication. I have reviewed Attachment 6 of the Apple Developer Program License Agreement, especially sections 2.1-2.5, and the snapshot documentation. I found guidance on static snapshots, but not a clear explanation of this MP4 export and end-user sharing scenario. Questions: Is either approach a supported, permitted use under the standard agreement and documentation? Is there an official document addressing it? Does the answer differ for standard versus satellite/hybrid or 3D views, or for a fixed map with an animated route versus a moving camera? How should attribution and the Legal link be handled in a non-interactive exported video, and are there specific limits on intermediate-frame retention or rendering frequency? If separate permission or a different implementation is required, which Apple team or support category should we contact? We have submitted a Rights and Permissions inquiry and would appreciate guidance on the correct channel for this MapKit-specific question. Apps such as ReRun advertise route-video export, and Huawei Health offers dynamic route videos. We do not know the map source used in every exported video or whether these apps have separate agreements, so we are not assuming their availability grants permission for our implementation. We are looking for the documented path available to other developers. Thank you for any official references or routing guidance. Rabia / RotaTakip
0
0
36
5d
MapKit & Maps Server API: Cross-Border Search Limitations in Mainland China
Hello, We are developing an application for users located in mainland China who need to plan outbound travel. Users need to search for locations outside mainland China and view rich information provided by Apple Maps services on a map. We have encountered certain limitations in MapKit’s behavior and would like to confirm the boundaries of the public API. Background and observations : Feedback report FB13557287 (originally filed on macOS 14.2) describes the following: when developers use MKLocalSearchCompleter, users in mainland China receive only results within mainland China. Searches for overseas locations such as “New York” or “Berlin” return no results, and using a VPN reportedly does not improve the situation. The developer quoted Apple’s response as “This is expected.” Is this still the expected behavior on the current versions of iOS/iPadOS/macOS 27? If the behavior has changed, what is the correct configuration? On the same device located in mainland China, the Apple Maps app can display overseas map data, and in our tests it can also return overseas locations. The China-region attribution page (https://gspe21-ssl.ls.apple.com/html/attribution-cn2-98.html) lists the data providers for mainland China and states, “Sources for map data outside China can be found here.” This appears to indicate that the Maps app uses a dual-data-source model combining mainland China data with global data. At the same time, we cannot find overseas locations in the “Add Location” feature of Reminders and Journal, which is consistent with the behavior we have observed in the public MapKit APIs. Questions : Can third-party applications obtain the same cross-border data capabilities as the Apple Maps app through public MapKit APIs? If so, which APIs, configurations, or entitlements are required? If not, is this an intentional design decision? Could this be explicitly documented in the MapKit documentation? Does the Maps app select its data source based on the map viewport or individual requests, while MapKit selects a single data source based on the device’s region? If so, do the public APIs allow an application to specify a data source per request? If public MapKit APIs cannot support this scenario, what architecture does Apple recommend as best practice? Are the same regional restrictions applicable to the Apple Maps Server API? Specifically, when /v1/search is called from a backend or account operating within mainland China’s network environment, can overseas results be returned when limitToCountries or searchRegion is configured? Does /v1/directions support cross-border routing? We are not asking about private APIs or seeking ways to bypass regional restrictions. Our goal is to understand the supported boundaries of the public APIs so that we can make appropriate product-design decisions. Thank you.
1
0
331
2w
Notification Delivery Issues for Location Push Service Extension
We are currently testing the implementation of our Location Push Service Extension (LPSE) in both Ad Hoc and Release environments. We have encountered an issue where LPSE notifications, which were previously working correctly, suddenly fail to be delivered on some devices. After a period of several hours, the notifications resume arriving, but the issue remains intermittent. Notably, during these periods of suspected delivery restriction, regular push notifications (e.g., those using apns-push-type: alert) are delivered and displayed without any problem. [Detailed Situation] Test Environment and Scope We are testing LPSE after obtaining the necessary entitlements, in both Ad Hoc and Release environments. The issue is not observed on all test devices; only certain devices are affected. Observed Behavior Under normal circumstances, LPSE notifications are received and the extension is activated; however, on some devices the notifications suddenly stop arriving. During these periods, even when sending notifications with apns-push-type: location directly via the CloudKit Push Notification Console, no response is observed on the affected devices. The APNs server (api.push.apple.com) always returns a 200 OK response via HTTP/2, and our server-side logs and configurations (DNS resolution performed on every request, using the same JWT token for 59 minutes per session, communication via HTTP/2 with ALPN Protocol: h2) show no issues. Other app functionalities (network communication, UI responsiveness, etc.) work normally. Sending content When sending notifications from our server to APNs (api.push.apple.com), we use the following configuration (over HTTP/2): const payload = { aps: { 'content-available': 1 } }; const headers = { ':method': 'POST', ':path': /3/device/${apnsToken}, 'Authorization': bearer ${jwtToken}, 'apns-topic': 'ot.Here.location-query', 'apns-priority': '10', 'apns-push-type': 'location', 'Content-Type': 'application/json' }; We perform DNS resolution for every request, use the same JWT token for a 59-minute period per session, and communicate via HTTP/2 with ALPN Protocol: h2. Hypothesis on the Cause We suspect that due to an implementation issue, silent push notifications (using content-available: 1) were being sent every few minutes concurrently, which may have triggered an APNs delivery restriction (rate limiting). As a countermeasure, we have completely stopped sending silent pushes and any other background notifications aside from LPSE; however, the issue persists. Additionally, even after resetting affected devices, the delivery problem continues to occur. [Questions for Diagnosis] Given the above situation, is it reasonable to suspect that excessive silent push notifications have triggered an APNs delivery restriction? Does such a silent push restriction affect LPSE notifications (i.e., those sent with apns-push-type: location)? Do APNs delivery restrictions persist even after a device has been reset? Can a high volume of LPSE notifications alone (without silent pushes) also trigger a delivery restriction? → This is our primary concern since it poses a significant implementation challenge. Please let us know if any additional information is required for diagnosis.
4
0
615
2w
addSubview slows down with sibling count, process-wide, once a MapKit location view has been in a window
Filed as FB25405148 with a small sample project. Posting here in case anyone else has hit this or knows a better workaround. Once a MapKit location view has been in a window, addSubview: anywhere in the process takes time proportional to the number of subviews the parent already has. The parent doesn't have to belong to the map. On iPhone Air with iOS 27.2, in a clean app, adding 8,000 plain UIViews to a plain UIView took 85 ms without a location view and 4,992 ms with one. You won't see this with a few hundred views. Up to about 1,000 siblings, the whole batch costs less than 100 ms extra. Map apps can hit it because annotation views are siblings under one container. On the same phone, adding 5,000 annotation views in batches took the longest frame from 25 ms to 208 ms. It happens with the default location view, with an MKUserLocationView returned from mapView(_:viewFor:), and with a bare MKUserLocationView added to a window by hand. A plain MKAnnotationView doesn't cause it. From LLDB on the simulator, it looks like MapKit's first call to _accessibilitySetInterfaceStyleIntent: installs _UIAccessibilityInterfaceStyleVisitor, and that's what slows later adds. Returning a plain MKAnnotationView for MKUserLocation avoids it, but gives up the system view. Only iOS 27.2 has been tested so far. Has anyone seen this on other versions, or found a way to keep the system location view without the cost?
0
0
77
2w
MKMapSnapshotter in personal PDF photo albums — clarification of permitted use and appropriate Apple contact
Hello, I am developing Partance, a native iOS/iPadOS application for planning trips and keeping a personal travel journal. The application already generates PDF souvenir albums containing the user’s photographs, captions and journal entries. Before adding static maps, I would like to identify official Apple guidance covering the intended use. Proposed feature The user would explicitly choose to include: one overview map showing the locations represented in their album; smaller maps accompanying individual journal entries. The maps would be generated using MKMapSnapshotter, with markers added by the application. The marker coordinates come from the user’s photographs already stored in their journal, rather than from saved Apple geocoding or search results. This would not be an offline-navigation feature, a downloadable map collection, a map database or a substitute mapping service. Personal use of the resulting PDF Each participant in a trip has their own personal journal and generates their own album. The resulting PDF: is intended as a personal souvenir, not for sale, publication or public distribution; may be retained indefinitely in Partance until the user explicitly deletes it; may also be saved in Files or transferred to the user’s own computer; may be printed at home or uploaded to a commercial photo-book printing service solely to manufacture the user’s personal physical album. Intermediate map images could be deleted after PDF generation. However, the map images embedded in the PDF would remain part of the user’s album. Documentation and uncertainty Apple’s archived “Location and Maps Programming Guide,” under “Creating a Snapshot of a Map,” explicitly describes using MKMapSnapshotter to implement printing: https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/LocationAwarenessPG/MapKit/MapKit.html However, Attachment 6 of the Apple Developer Program License Agreement, particularly sections 2.1, 2.3 and 2.5, leaves me uncertain about retaining the generated images permanently inside a personal PDF: https://developer.apple.com/support/terms/apple-developer-program-license-agreement/ My questions are: Is there official Apple guidance confirming whether this specific use is permitted, including indefinite retention of the personal PDF? Is there a documented distinction between retaining map data as an application cache and retaining a snapshot within a user-generated document? What attribution, logos or legal notices must accompany the maps in the PDF and printed album, including any requirements relating to Apple’s data providers? Does using a commercial printing service solely to produce the user’s personal photo book require any additional permission? If these questions cannot be answered here, which Apple team or contact channel should handle them? I have already submitted a request through Apple’s Rights and Permissions form and received an automatic acknowledgement only. The map-export feature has not been implemented. I am seeking an official documentation reference or the appropriate Apple contact, rather than asking other developers to provide a legal opinion. Thank you for your help.
0
0
68
2w
CLMonitor delivers duplicate events for CircularGeographicCondition when the app is launched in the background
I’m seeing CLMonitor deliver the same event twice when a CircularGeographicCondition triggers while the app is not running and the system launches it in the background. The two events have the same identifier, state, date and diagnostic data. When the app is in the foreground, I get exactly one event per transition. I've included a minimum example as an attachment. It creates a CLServiceSession and CLMonitor in application(_:didFinishLaunchingWithOptions:) and observes their events. Here is a log from a background launch (trimmed to the relevant fields) 15:34:13.742Z App didFinishLaunchingWithOptions: none 15:34:13.784Z CLServiceSession.Diagnostic(all false) 15:34:13.784Z Started monitor 15:34:13.794Z event: identifier: 0DE4B7F8-..., state: satisfied, date: 15:34:13.559Z 15:34:13.795Z event: identifier: 0DE4B7F8-..., state: satisfied, date: 15:34:13.559ZThe two events are identical (including date) and arrive about 1 ms apart. All diagnostic flags on both the event and the service session are false. What I’ve ruled out / observations Not a repeated state with new diagnostics. The “Monitoring location changes with Core Location” sample project de-duplicates events whose state matches the previous one, noting that the only new information would be in diagnostics. That doesn’t explain this: the diagnostics are all false, the date is identical, and I don’t see the duplicate in the foreground. Scales with condition count. With two overlapping conditions, a single boundary crossing produces four events (two per condition) when launched in the background. The behavior occurs both on a simulator and on a real device The only reference to this behavior I was able to find is this StackOverflow post which was asked when iOS 6 was the latest My questions is: Is this duplicate delivery expected when CLMonitor is created in response to a background launch? Or does this indicate I have something set up incorrectly?
0
1
153
3w
Physical iPhone location simulation: Find My, persistence, and recovery
I'm developing a location-testing workflow for an owner-authorized physical iPhone using Xcode 27.0 and CoreDevice 642.16. The installed devicectl device simulate location coordinate and clear commands are available. The installed help states that simulation continues until cleared and describes clearing as returning to actual location. Before proceeding with physical-device testing, I'd appreciate clarification on five questions: Persistence: Does location simulation remain active after USB disconnection, termination of the developer connection, Mac sleep, or Mac shutdown? Find My: Does this simulation affect Find My People / My Location, Find My Devices, both, or neither? Is either behavior officially supported? Recovery: If clearing fails or the initiating Mac is unavailable, what supported procedure restores actual location? Remote control: Can an authorized developer change or clear the simulated location when the Mac and iPhone are geographically separated and on different networks? Standalone operation: Is there any documented API, entitlement, or device-management capability allowing an installed iPhone app to control system-wide simulated location independently of a Mac? I'm seeking documented behavior and a safe, reversible testing procedure, particularly where Find My and recovery are concerned. Thank you for any guidance or official documentation.
1
0
148
3w
iOS Background Location / Geofencing for Automatic Attendance — App Not Triggering Reliably
iOS Background Location / Geofencing for Automatic Attendance — App Not Triggering Reliably We are developing an enterprise attendance application called Attendo, which uses location-based geofencing for automatic employee check-in/check-out. Business requirement The application needs to work as follows: An employee is assigned an office/work location with a defined radius. When the employee enters the configured radius, the application should automatically record a Check-In. When the employee leaves the radius, the application should automatically record a Check-Out. This should happen without the employee having to open the application. The functionality needs to work even when the application is in the background and, where supported by iOS, after the application has been terminated. For example: «Office geofence = 200 meters Employee enters the 200 m radius → automatic Check-In Employee leaves the 200 m radius → automatic Check-Out» Current iOS implementation We are using iOS location services with: Location permission: Always Precise Location: enabled Background Location capability enabled Background location updates enabled Geofencing / region monitoring The application is intended to respond to location/geofence events without requiring the user to open the app. However, we are seeing cases where the application does not reliably receive/process the required location/geofence event when the application has been in the background for an extended period. The same business workflow works more reliably while the application is active. Our concern Our understanding is that iOS does not allow an application to maintain a continuously running background service in the same way that Android can. However, our requirement does not necessarily require continuous GPS polling if there is an Apple-supported mechanism that can reliably wake/relaunch the application when a user crosses a geofence. We would therefore like to understand the recommended architecture for this use case. Questions Is Core Location Region Monitoring the recommended mechanism for an enterprise geofencing application that needs to detect entry/exit while the app is not running? Can iOS relaunch the application after it has been terminated by the user/system when a monitored region is entered or exited? Is there any supported way to guarantee that an application will continue receiving location/geofence events after it has been in the background for a long period? Does enabling: "UIBackgroundModes = location" "allowsBackgroundLocationUpdates" "CLLocationManager" Region Monitoring provide the expected behavior, or are there additional requirements/configurations we should consider? Are there known limitations regarding: Low Power Mode device movement speed GPS/location accuracy stationary devices iOS terminating/suspending the application force-quitting the application from the App Switcher large/small geofence radius multiple monitored regions Is it possible to use significant-change location updates + region monitoring together for this type of attendance workflow? For an enterprise application where the user explicitly grants Always Allow Location permission and Precise Location is enabled, what level of reliability can realistically be expected from iOS geofencing? Important business constraint We cannot require employees to manually open the application every time they arrive at or leave the workplace. The objective is an automatic attendance system, where the employee's entry and exit from the workplace geofence is detected by iOS and the application records the corresponding attendance event. We understand that iOS is designed to protect battery life and user privacy and that continuous background execution may not be permitted. We are therefore looking for the Apple-recommended architecture for achieving this requirement using supported iOS APIs, rather than trying to circumvent iOS background execution policies. Any guidance from Apple engineers or developers who have implemented reliable enterprise geofencing would be greatly appreciated.
1
0
559
3w
CLLocation acquisition time: supported monotonic timestamp or bounded age conversion on iOS 16+?
For an application supporting iOS 16 and later, is there a supported public API that exposes a monotonic timestamp for the original determination of a CLLocation, rather than the time it is delivered to CLLocationManagerDelegate? The requirement is to reject observations whose original acquisition age exceeds 10,000,000,000 ns at the final native transport-dispatch check. Exactly 10 seconds is allowed; 10 seconds plus 1 ns is rejected before conversion to milliseconds. This is an arithmetic boundary requirement, not an assumption that location measurements have nanosecond physical accuracy. CLLocation.timestamp is a Date for when the location was determined. Sampling a continuous monotonic clock in didUpdateLocations instead measures callback receipt. Cached observations, batched updates and delayed background delivery can separate those events. Does a public API provide either: A monotonic acquisition/determination timestamp associated with that same CLLocation; or A documented finite uncertainty bound and supported method for relating its Date timestamp to a sleep-inclusive monotonic clock at dispatch? How do the documented guarantees handle wall-clock adjustments between determination and delivery, device sleep, suspension, queued updates and process restarts? If a newer API supplies stronger evidence, what is its minimum supported iOS version? If neither mechanism is available, is there a supported request or delivery mode that establishes a documented lower bound on the original determination time and can reliably reject older cached observations? A recent callback or request by itself would not establish that relationship. I would appreciate documentation describing the guarantees, limitations or supported alternatives. I have not established that such a mechanism is impossible; this is a capability clarification, not a claim of a reproduced operating-system defect.
1
0
149
3w
Location Services stopped working across the system on macOS
MacBook Air (M4) Current build: macOS 27 Developer Beta (26A5368g) I have a system-wide Location Services failure affecting Apple Maps, Safari geolocation APIs, and any application requesting the current location. Symptoms: Apple Maps cannot determine current location. Safari and browser geolocation APIs fail. Websites report that location cannot be found. Location Services are enabled and permissions are granted. The issue has persisted across: macOS 26.5 beta macOS 26.6 beta macOS 26.6 beta 2 macOS 27 Developer Beta Troubleshooting already performed: Multiple Wi-Fi networks tested. iPhone hotspot tested. VPN enabled and disabled. Location Services reset. Permissions reset and reauthorized. New clean local user account created (no Apple ID, no third-party software). Issue reproduces identically in the clean account. Technical observations: locationd logs repeatedly show: knownCount = 0 AlsWifi = unknown while Wi-Fi scanning itself appears successful: queryMacAddresses.size = 57 The system sees dozens of nearby access points, but none appear to be recognized for Wi-Fi positioning. Additional findings: Wi-Fi hardware functions normally. Internet connectivity is normal. Bluetooth and Find My device presence work. GeoServices resources are present on disk. No successful location fix is ever produced. Has anyone seen similar CoreLocation / GeoServices behavior where Wi-Fi scans succeed but knownCount always remains 0 and no location fix is generated?
11
2
2.2k
3w
System-wide Core Location failure on macOS 27.0.1: Wi-Fi positioning knownCount=0, incorrect time zone, same failure on Wi-Fi-only iPad
I am experiencing a system-wide Location Services failure on my MacBook running macOS 27.0.1. Several days after the problem first appeared on the Mac, my iPad Pro (Wi-Fi-only model) developed a very similar issue. Both devices are in Ukraine and should use the Europe/Kyiv time zone. The Mac unexpectedly selected Cupertino, PDT, while the iPad selected a Chinese time zone. Location detection is now failing in Apple Maps, Weather, browsers, and other applications using Core Location. My iPhone continues to determine its location correctly. The macOS locationd diagnostic logs show that Wi-Fi access points are being discovered but none are recognized as known references in the observed positioning check. Steps to reproduce Connect the affected Mac to a working Wi-Fi network with internet access. Ensure Location Services are enabled. Open Apple Maps and request the current location. Attempt browser-based geolocation using a website that requests the current location. Open System Settings → General → Date & Time and enable automatic time-zone detection. Observe the inability to determine the correct location and the incorrect automatic time-zone selection. The failure persists across multiple Wi-Fi networks, including an iPhone Personal Hotspot. Expected result Core Location should correctly determine the approximate physical location in Ukraine using available positioning information. Apple Maps, Weather, browsers, and other applications should receive valid location data. Automatic time-zone detection should select Europe/Kyiv. Actual result Apple Maps cannot correctly determine the current location. Browser geolocation fails. Weather displays incorrect location-dependent information. Automatic time-zone detection selected Cupertino (PDT) on the Mac instead of Europe/Kyiv. The Wi-Fi-only iPad Pro independently selected a Chinese time zone instead of Europe/Kyiv. Automatic location detection remains unusable across applications. The problem persists after connecting to different Wi-Fi networks. The Mac problem began suddenly during normal use. Around that time, the system automatically transitioned to dark appearance for the evening (as expected), but the automatic time zone also changed unexpectedly. The iPad developed similar symptoms several days later. Troubleshooting already performed Tested multiple Wi-Fi networks. Tested internet access through an iPhone Personal Hotspot. Checked IP-based geolocation using external services; these correctly identify the geographic region. Considered VPN-related causes; the behavior is not explained by the IP geolocation results. Confirmed that Location Services work correctly on my iPhone. The simultaneous involvement of two independent devices, combined with normal iPhone positioning, suggests a possible failure in Wi-Fi-based positioning or the associated system services rather than an isolated hardware issue. Technical diagnostics On October 22, 2026, the following message was obtained from the macOS locationd unified log: 2026-10-22 22:31:00.638 Df locationd[387:2755b6] [com.apple.locationd.Position:GeneralCLX] WifiAps, querycheck, knownCount, 0, unknownCount, 17, knownCountTile, 0, knownToUnknownRatio, 0.0, queryMacAddresses.size, 34, sinceLastServerQuery, 187.15, isQueryNeeded, 1, forceQuery, 0, queryType, 0, reqType, 0 Important diagnostic fields: knownCount = 0 unknownCount = 17 knownCountTile = 0 knownToUnknownRatio = 0.0 queryMacAddresses.size = 34 isQueryNeeded = 1 These values indicate that the positioning subsystem is discovering Wi-Fi access points but has no recognized positioning references in this particular check. This resembles a previously reported Core Location / GeoServices failure. Potentially related existing reports Apple Developer Forums: https://developer.apple.com/forums/thread/835896 The discussion documents a similar system-wide location failure with knownCount = 0 despite successful Wi-Fi scanning. Feedback IDs submitted by another affected user: FB23196632 FB23366087 There are also independent reports from Ukrainian users whose Macs incorrectly determine their location or time zone as China: https://www.reddit.com/r/MacOS/comments/1nt0lli/location_glitch/ These reports may involve the same underlying issue, but a common root cause has not been confirmed. Request for investigation Please investigate whether this issue is related to: Apple's Wi-Fi positioning database or lookup service. Core Location / GeoServices processing of Wi-Fi-based location results. Incorrect, missing, or stale Wi-Fi access-point location records. Local positioning cache or Wi-Fi regulatory-domain problems. I would particularly appreciate investigation of the knownCount = 0 condition and whether it can explain the incorrect time-zone selection on two separate devices. Please route this report to the appropriate macOS Core Location / GeoServices engineering team. I can provide additional diagnostic logs and sysdiagnose data if required.
1
0
960
4w
How to pass off liveUpdates(_:) to main app
Hello! I was looking through Apple's documentation about Core Location and the Location Push Service Extension, and it seems like you can 'pass-off' liveUpdates(_:) to the main app (yes, that's simplified), but they don't seem to explain what that means, and any way on how to do it. Do they just mean like a SLC, or silent push? I am just curious, because it isn't clear at all what they mean. Thanks!
1
0
199
Oct ’26
GPS not working after iPadOS 27 upgrade on iPad Cellular Gen 9
There is a post out on the main community page (https://discussions.apple.com/thread/256371563?answerId=262162384022&sortBy=rank#262162384022) that discusses several users with issues around the GPS not working after the iPadOS 27 update on Gen 9 iPads. I also ran into this. I did everything mentioned in the community post (including completely wiping my iPad) and nothing worked. However, I did try updating to 27.2 Beta 4 and it seems to have fixed the issue. Is there a specific fix for the GPS not working on an iPad Gen 9 after upgrading to iPadOS 27 in 27.2? I'm thrilled it is working again, but wondering if it's just a fluke or if something really was addressed?
0
1
125
Oct ’26
Unexpected Immediate Delivery of Multiple UNLocationTrigger Notifications
Hello, I'm encountering an issue with UNLocationNotificationTrigger in my iOS app. I've scheduled three local notifications using UNLocationNotificationTrigger, each tied to a distinct geographic region. These regions are significantly distant from one another and should not trigger simultaneously under normal movement conditions. However, during testing, the user received all three notifications within one second, despite being physically located near only one of the regions. This behavior is unexpected and defeats the purpose of using location-based triggers. Could you please clarify why this might be happening? Is there a known issue with UNLocationTrigger, or is there a possibility that iOS preemptively triggers all scheduled location notifications? Any guidance or recommended practices to avoid this behavior would be greatly appreciated. Thank you!
6
0
997
Oct ’26
Title Location updates stop or become highly inaccurate during navigation on iOS / iPadOS 27 Body We develop and operate a navigation app. Since updating to iOS / iPadOS 27, several users have reported that location updates stop during navigation,
I'm working on a navigation app. Since updating to iOS / iPadOS 27, several users have reported that location updates stop during navigation, or that the displayed location is far from where they actually are. Some users say the same thing happens in Apple Maps and Google Maps, so the cause seems to be in the OS rather than in any particular app's implementation. Reported symptoms The current location stops updating, or updates intermittently, during navigation The current location is shown far away from the user's actual position Reported devices and OS versions Almost all reports come from the iPad (9th generation), but the issue also occurs on iPhone. iPad (9th generation) Wi-Fi + Cellular / iPadOS 27.0 iPhone 16 Pro Max / iOS 27.0 iPhone 16 Pro / iOS 27.2 Public Beta iPhone 17 / iOS 27.0 Suggested workarounds (none resolved the issue) None of the following steps suggested to users helped: Checking location permissions ("While Using the App" or "Always", with "Precise Location" turned on) Turning Location Services off and on again Restarting the device Using "Reset Location & Privacy" Questions Has anyone else received similar reports on iOS / iPadOS 27? Any app-side workarounds would be greatly appreciated.
0
1
404
Oct ’26
MKMapItem addressRepresentations fullAddress singleLine does not always work and provides the address in multiline
Hello, I’m trying to display in my app the full address of an MKMapItem in a single line. I notice the following function does not always return single line but contains newlines. https://developer.apple.com/documentation/mapkit/mkaddressrepresentations/fulladdress(includingregion:singleline:) I provide the list of some identifiers so you can check what’s wrong. "I39866265D4A8562A", // 🟢 works "IF233A1E949A5566C", // 🟢 works "ICA31B6B98E02A528", // 🔴 does not work "ICA31B6B98E02A528", // 🔴 does not work "I9E00A04BFCB9718D", // 🔴 does not work "IFACDC4BC25712413", // 🔴 does not work "I74135A4F7C7FE654", // 🔴 does not work "IFE4A3BC4FEFA53E0", // 🔴 does not work You can check this FB25681688 Thank you, Regards, Axel
Replies
0
Boosts
0
Views
4
Activity
39m
[iOS 27.2.1 / iPhone 17 Pro] BLE Central app sporadically fails to detect region and interact with Peripheral
Hello everyone, I am developing a BLE-based room entry/exit authentication app and we are currently experiencing an intermittent issue where the app fails to respond to the reader. I am looking for any similar reports or potential workarounds. [Environment] Devices affected: iPhone 17 Pro (majority of user reports), iPhone Air (reproduced once internally) OS Version: iOS 27.2.1 [App Architecture] iOS App: Central Reader (Hardware): Peripheral [Issue Description] On the specific devices mentioned above, the reader and the iOS app sporadically fail to interact with each other. This unresponsiveness occurs at a frequency of approximately 1 out of 5 attempts. [Investigation Details] Our development team was able to reproduce this exact issue once on an iPhone Air. When analyzing the logs and behavior during this reproduction, we confirmed that although the device was physically well within the BLE region (range), the OS completely failed to detect that it was inside the region. [Questions] Is this a known bug regarding CoreBluetooth / CoreLocation region monitoring specific to iOS 27.2.1 or newer devices like the iPhone 17 Pro? If anyone has experienced this intermittent region detection failure on recent OS/device combinations, are there any known workarounds to force the detection or prevent the drops? Any insights or advice would be greatly appreciated. Thank you!
Replies
0
Boosts
0
Views
78
Activity
2d
Can’t submit IMDF! Approved for Indoor Maps Program, no upload path in ABR.
Has anyone recently found a working path to claim a venue and upload an IMDF in Apple Business Register? Our Locations page shows 0 locations with no option to add one. (Screenshot attached.) Our business is approved for the Indoor Maps Program, our location is approved/verified in Apple Business Register, and our IMDF file is complete and ready to submit. We just can’t find anywhere to submit it. The 2019 WWDC session “Introducing the Indoor Maps Program” shows a “Claim your location” flow and a per-venue upload dashboard that simply doesn’t exist in our account today. We emailed maps-indoor-support@apple.com on August 25 with no response. A few other threads here describe the same thing, IMDF or venue registration stuck with no visible next step, so this doesn’t look isolated to our account. Any pointers on where this actually happens now would help. This has been open almost three months with a completed file and nowhere to send it. I am trying to develop my app but cannot proceed without this piece.
Replies
0
Boosts
0
Views
45
Activity
2d
MapKit JS token returns 401 only for mainland China while Apple's official sample works
Hello Apple engineers, Feedback Assistant report: FB25612837 (submitted under our developer team). We are investigating a production Web MapKit JS authorization failure. Our native iOS App works normally; this report concerns Web MapKit JS only. Observed on 14 November 2026: Our portal-generated MapKit JS token returned HTTP 401 for mainland-China bootstrap authorization and HTTP 200 for US authorization. Apple's official embedded-map example worked in the same browser and network, returning countryCode CN and displaying Amap attribution. A minimal page using SDK 6.1.205 on our production Web domain also returned 401. SDK 5.81.72 had the same result. Exact-domain, wildcard-domain, expiring, and temporarily unrestricted diagnostic tokens produced the same China-only failure. The unrestricted token was revoked immediately after the test and was never deployed. Rechecked on 17 November 2026: The locally configured production token, whose hash matches the token inspected in production on 14 November, still returns HTTP 401 with {"error":{"message":"Not Authorized","details":[]}}. It uses ES256, scope mapkit_js, and an origin matching our Web domain pattern. It is not expired and has no duplicate header or payload claims. Separately configured root-domain MapKit JS tokens also return 401 when tested with their matching origin. These 17 November probes used locally configured tokens; the authenticated production token value was not freshly read back that day. We found matching reports: https://developer.apple.com/forums/thread/766180 https://developer.apple.com/forums/thread/748764 https://developer.apple.com/forums/thread/684701 We checked the duplicate-claims fix described here and ruled it out for our configured token: https://developer.apple.com/forums/thread/113670 Questions: Is any additional team provisioning or authorization required for the mainland-China MapKit JS service? Can regional validation treat portal-generated tokens differently, despite the same token being accepted by another region? Is there a supported corrective configuration we can apply? We have not found one in the current Maps token documentation. Developer Support case 30000015236904 directed us to the forums. We can provide account-specific details privately through Feedback Assistant. This public question intentionally omits tokens, private keys, account identifiers, customer data, and production logs.
Replies
0
Boosts
0
Views
51
Activity
4d
MapKit route animation exported to MP4: permitted use and appropriate Apple contact
Hello, I am Rabia, publisher of RotaTakip, a pre-launch iOS outdoor GPS app being developed with my son. We are evaluating Apple Maps for a user-initiated route-video feature and would appreciate a reference to official guidance or the appropriate Apple contact before enabling it. Proposed use: A user selects their own recorded GPS route and creates a short animated recap over an Apple map. The app saves an MP4 to Photos, and the user may share it on social media or play it on non-Apple devices. Rendering would happen on the user's device using public APIs. Required Apple and third-party attribution would remain visible. We would not extract raw tiles, scrape map data, build a map database, or perform bulk/server-side rendering. The app is planned as a paid, one-time-purchase GPS app. The map would be a main visual element in the exported recap. Video export remains disabled pending clarification. We are considering two approaches separately: MKMapSnapshotter images with our own route overlays, potentially a sequence of camera views, encoded with AVFoundation. A user-initiated ReplayKit recording of an animated MKMapView, with the required system consent and recording indication. I have reviewed Attachment 6 of the Apple Developer Program License Agreement, especially sections 2.1-2.5, and the snapshot documentation. I found guidance on static snapshots, but not a clear explanation of this MP4 export and end-user sharing scenario. Questions: Is either approach a supported, permitted use under the standard agreement and documentation? Is there an official document addressing it? Does the answer differ for standard versus satellite/hybrid or 3D views, or for a fixed map with an animated route versus a moving camera? How should attribution and the Legal link be handled in a non-interactive exported video, and are there specific limits on intermediate-frame retention or rendering frequency? If separate permission or a different implementation is required, which Apple team or support category should we contact? We have submitted a Rights and Permissions inquiry and would appreciate guidance on the correct channel for this MapKit-specific question. Apps such as ReRun advertise route-video export, and Huawei Health offers dynamic route videos. We do not know the map source used in every exported video or whether these apps have separate agreements, so we are not assuming their availability grants permission for our implementation. We are looking for the documented path available to other developers. Thank you for any official references or routing guidance. Rabia / RotaTakip
Replies
0
Boosts
0
Views
36
Activity
5d
MapKit & Maps Server API: Cross-Border Search Limitations in Mainland China
Hello, We are developing an application for users located in mainland China who need to plan outbound travel. Users need to search for locations outside mainland China and view rich information provided by Apple Maps services on a map. We have encountered certain limitations in MapKit’s behavior and would like to confirm the boundaries of the public API. Background and observations : Feedback report FB13557287 (originally filed on macOS 14.2) describes the following: when developers use MKLocalSearchCompleter, users in mainland China receive only results within mainland China. Searches for overseas locations such as “New York” or “Berlin” return no results, and using a VPN reportedly does not improve the situation. The developer quoted Apple’s response as “This is expected.” Is this still the expected behavior on the current versions of iOS/iPadOS/macOS 27? If the behavior has changed, what is the correct configuration? On the same device located in mainland China, the Apple Maps app can display overseas map data, and in our tests it can also return overseas locations. The China-region attribution page (https://gspe21-ssl.ls.apple.com/html/attribution-cn2-98.html) lists the data providers for mainland China and states, “Sources for map data outside China can be found here.” This appears to indicate that the Maps app uses a dual-data-source model combining mainland China data with global data. At the same time, we cannot find overseas locations in the “Add Location” feature of Reminders and Journal, which is consistent with the behavior we have observed in the public MapKit APIs. Questions : Can third-party applications obtain the same cross-border data capabilities as the Apple Maps app through public MapKit APIs? If so, which APIs, configurations, or entitlements are required? If not, is this an intentional design decision? Could this be explicitly documented in the MapKit documentation? Does the Maps app select its data source based on the map viewport or individual requests, while MapKit selects a single data source based on the device’s region? If so, do the public APIs allow an application to specify a data source per request? If public MapKit APIs cannot support this scenario, what architecture does Apple recommend as best practice? Are the same regional restrictions applicable to the Apple Maps Server API? Specifically, when /v1/search is called from a backend or account operating within mainland China’s network environment, can overseas results be returned when limitToCountries or searchRegion is configured? Does /v1/directions support cross-border routing? We are not asking about private APIs or seeking ways to bypass regional restrictions. Our goal is to understand the supported boundaries of the public APIs so that we can make appropriate product-design decisions. Thank you.
Replies
1
Boosts
0
Views
331
Activity
2w
Notification Delivery Issues for Location Push Service Extension
We are currently testing the implementation of our Location Push Service Extension (LPSE) in both Ad Hoc and Release environments. We have encountered an issue where LPSE notifications, which were previously working correctly, suddenly fail to be delivered on some devices. After a period of several hours, the notifications resume arriving, but the issue remains intermittent. Notably, during these periods of suspected delivery restriction, regular push notifications (e.g., those using apns-push-type: alert) are delivered and displayed without any problem. [Detailed Situation] Test Environment and Scope We are testing LPSE after obtaining the necessary entitlements, in both Ad Hoc and Release environments. The issue is not observed on all test devices; only certain devices are affected. Observed Behavior Under normal circumstances, LPSE notifications are received and the extension is activated; however, on some devices the notifications suddenly stop arriving. During these periods, even when sending notifications with apns-push-type: location directly via the CloudKit Push Notification Console, no response is observed on the affected devices. The APNs server (api.push.apple.com) always returns a 200 OK response via HTTP/2, and our server-side logs and configurations (DNS resolution performed on every request, using the same JWT token for 59 minutes per session, communication via HTTP/2 with ALPN Protocol: h2) show no issues. Other app functionalities (network communication, UI responsiveness, etc.) work normally. Sending content When sending notifications from our server to APNs (api.push.apple.com), we use the following configuration (over HTTP/2): const payload = { aps: { 'content-available': 1 } }; const headers = { ':method': 'POST', ':path': /3/device/${apnsToken}, 'Authorization': bearer ${jwtToken}, 'apns-topic': 'ot.Here.location-query', 'apns-priority': '10', 'apns-push-type': 'location', 'Content-Type': 'application/json' }; We perform DNS resolution for every request, use the same JWT token for a 59-minute period per session, and communicate via HTTP/2 with ALPN Protocol: h2. Hypothesis on the Cause We suspect that due to an implementation issue, silent push notifications (using content-available: 1) were being sent every few minutes concurrently, which may have triggered an APNs delivery restriction (rate limiting). As a countermeasure, we have completely stopped sending silent pushes and any other background notifications aside from LPSE; however, the issue persists. Additionally, even after resetting affected devices, the delivery problem continues to occur. [Questions for Diagnosis] Given the above situation, is it reasonable to suspect that excessive silent push notifications have triggered an APNs delivery restriction? Does such a silent push restriction affect LPSE notifications (i.e., those sent with apns-push-type: location)? Do APNs delivery restrictions persist even after a device has been reset? Can a high volume of LPSE notifications alone (without silent pushes) also trigger a delivery restriction? → This is our primary concern since it poses a significant implementation challenge. Please let us know if any additional information is required for diagnosis.
Replies
4
Boosts
0
Views
615
Activity
2w
addSubview slows down with sibling count, process-wide, once a MapKit location view has been in a window
Filed as FB25405148 with a small sample project. Posting here in case anyone else has hit this or knows a better workaround. Once a MapKit location view has been in a window, addSubview: anywhere in the process takes time proportional to the number of subviews the parent already has. The parent doesn't have to belong to the map. On iPhone Air with iOS 27.2, in a clean app, adding 8,000 plain UIViews to a plain UIView took 85 ms without a location view and 4,992 ms with one. You won't see this with a few hundred views. Up to about 1,000 siblings, the whole batch costs less than 100 ms extra. Map apps can hit it because annotation views are siblings under one container. On the same phone, adding 5,000 annotation views in batches took the longest frame from 25 ms to 208 ms. It happens with the default location view, with an MKUserLocationView returned from mapView(_:viewFor:), and with a bare MKUserLocationView added to a window by hand. A plain MKAnnotationView doesn't cause it. From LLDB on the simulator, it looks like MapKit's first call to _accessibilitySetInterfaceStyleIntent: installs _UIAccessibilityInterfaceStyleVisitor, and that's what slows later adds. Returning a plain MKAnnotationView for MKUserLocation avoids it, but gives up the system view. Only iOS 27.2 has been tested so far. Has anyone seen this on other versions, or found a way to keep the system location view without the cost?
Replies
0
Boosts
0
Views
77
Activity
2w
MKMapSnapshotter in personal PDF photo albums — clarification of permitted use and appropriate Apple contact
Hello, I am developing Partance, a native iOS/iPadOS application for planning trips and keeping a personal travel journal. The application already generates PDF souvenir albums containing the user’s photographs, captions and journal entries. Before adding static maps, I would like to identify official Apple guidance covering the intended use. Proposed feature The user would explicitly choose to include: one overview map showing the locations represented in their album; smaller maps accompanying individual journal entries. The maps would be generated using MKMapSnapshotter, with markers added by the application. The marker coordinates come from the user’s photographs already stored in their journal, rather than from saved Apple geocoding or search results. This would not be an offline-navigation feature, a downloadable map collection, a map database or a substitute mapping service. Personal use of the resulting PDF Each participant in a trip has their own personal journal and generates their own album. The resulting PDF: is intended as a personal souvenir, not for sale, publication or public distribution; may be retained indefinitely in Partance until the user explicitly deletes it; may also be saved in Files or transferred to the user’s own computer; may be printed at home or uploaded to a commercial photo-book printing service solely to manufacture the user’s personal physical album. Intermediate map images could be deleted after PDF generation. However, the map images embedded in the PDF would remain part of the user’s album. Documentation and uncertainty Apple’s archived “Location and Maps Programming Guide,” under “Creating a Snapshot of a Map,” explicitly describes using MKMapSnapshotter to implement printing: https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/LocationAwarenessPG/MapKit/MapKit.html However, Attachment 6 of the Apple Developer Program License Agreement, particularly sections 2.1, 2.3 and 2.5, leaves me uncertain about retaining the generated images permanently inside a personal PDF: https://developer.apple.com/support/terms/apple-developer-program-license-agreement/ My questions are: Is there official Apple guidance confirming whether this specific use is permitted, including indefinite retention of the personal PDF? Is there a documented distinction between retaining map data as an application cache and retaining a snapshot within a user-generated document? What attribution, logos or legal notices must accompany the maps in the PDF and printed album, including any requirements relating to Apple’s data providers? Does using a commercial printing service solely to produce the user’s personal photo book require any additional permission? If these questions cannot be answered here, which Apple team or contact channel should handle them? I have already submitted a request through Apple’s Rights and Permissions form and received an automatic acknowledgement only. The map-export feature has not been implemented. I am seeking an official documentation reference or the appropriate Apple contact, rather than asking other developers to provide a legal opinion. Thank you for your help.
Replies
0
Boosts
0
Views
68
Activity
2w
CLMonitor delivers duplicate events for CircularGeographicCondition when the app is launched in the background
I’m seeing CLMonitor deliver the same event twice when a CircularGeographicCondition triggers while the app is not running and the system launches it in the background. The two events have the same identifier, state, date and diagnostic data. When the app is in the foreground, I get exactly one event per transition. I've included a minimum example as an attachment. It creates a CLServiceSession and CLMonitor in application(_:didFinishLaunchingWithOptions:) and observes their events. Here is a log from a background launch (trimmed to the relevant fields) 15:34:13.742Z App didFinishLaunchingWithOptions: none 15:34:13.784Z CLServiceSession.Diagnostic(all false) 15:34:13.784Z Started monitor 15:34:13.794Z event: identifier: 0DE4B7F8-..., state: satisfied, date: 15:34:13.559Z 15:34:13.795Z event: identifier: 0DE4B7F8-..., state: satisfied, date: 15:34:13.559ZThe two events are identical (including date) and arrive about 1 ms apart. All diagnostic flags on both the event and the service session are false. What I’ve ruled out / observations Not a repeated state with new diagnostics. The “Monitoring location changes with Core Location” sample project de-duplicates events whose state matches the previous one, noting that the only new information would be in diagnostics. That doesn’t explain this: the diagnostics are all false, the date is identical, and I don’t see the duplicate in the foreground. Scales with condition count. With two overlapping conditions, a single boundary crossing produces four events (two per condition) when launched in the background. The behavior occurs both on a simulator and on a real device The only reference to this behavior I was able to find is this StackOverflow post which was asked when iOS 6 was the latest My questions is: Is this duplicate delivery expected when CLMonitor is created in response to a background launch? Or does this indicate I have something set up incorrectly?
Replies
0
Boosts
1
Views
153
Activity
3w
Physical iPhone location simulation: Find My, persistence, and recovery
I'm developing a location-testing workflow for an owner-authorized physical iPhone using Xcode 27.0 and CoreDevice 642.16. The installed devicectl device simulate location coordinate and clear commands are available. The installed help states that simulation continues until cleared and describes clearing as returning to actual location. Before proceeding with physical-device testing, I'd appreciate clarification on five questions: Persistence: Does location simulation remain active after USB disconnection, termination of the developer connection, Mac sleep, or Mac shutdown? Find My: Does this simulation affect Find My People / My Location, Find My Devices, both, or neither? Is either behavior officially supported? Recovery: If clearing fails or the initiating Mac is unavailable, what supported procedure restores actual location? Remote control: Can an authorized developer change or clear the simulated location when the Mac and iPhone are geographically separated and on different networks? Standalone operation: Is there any documented API, entitlement, or device-management capability allowing an installed iPhone app to control system-wide simulated location independently of a Mac? I'm seeking documented behavior and a safe, reversible testing procedure, particularly where Find My and recovery are concerned. Thank you for any guidance or official documentation.
Replies
1
Boosts
0
Views
148
Activity
3w
iOS Background Location / Geofencing for Automatic Attendance — App Not Triggering Reliably
iOS Background Location / Geofencing for Automatic Attendance — App Not Triggering Reliably We are developing an enterprise attendance application called Attendo, which uses location-based geofencing for automatic employee check-in/check-out. Business requirement The application needs to work as follows: An employee is assigned an office/work location with a defined radius. When the employee enters the configured radius, the application should automatically record a Check-In. When the employee leaves the radius, the application should automatically record a Check-Out. This should happen without the employee having to open the application. The functionality needs to work even when the application is in the background and, where supported by iOS, after the application has been terminated. For example: «Office geofence = 200 meters Employee enters the 200 m radius → automatic Check-In Employee leaves the 200 m radius → automatic Check-Out» Current iOS implementation We are using iOS location services with: Location permission: Always Precise Location: enabled Background Location capability enabled Background location updates enabled Geofencing / region monitoring The application is intended to respond to location/geofence events without requiring the user to open the app. However, we are seeing cases where the application does not reliably receive/process the required location/geofence event when the application has been in the background for an extended period. The same business workflow works more reliably while the application is active. Our concern Our understanding is that iOS does not allow an application to maintain a continuously running background service in the same way that Android can. However, our requirement does not necessarily require continuous GPS polling if there is an Apple-supported mechanism that can reliably wake/relaunch the application when a user crosses a geofence. We would therefore like to understand the recommended architecture for this use case. Questions Is Core Location Region Monitoring the recommended mechanism for an enterprise geofencing application that needs to detect entry/exit while the app is not running? Can iOS relaunch the application after it has been terminated by the user/system when a monitored region is entered or exited? Is there any supported way to guarantee that an application will continue receiving location/geofence events after it has been in the background for a long period? Does enabling: "UIBackgroundModes = location" "allowsBackgroundLocationUpdates" "CLLocationManager" Region Monitoring provide the expected behavior, or are there additional requirements/configurations we should consider? Are there known limitations regarding: Low Power Mode device movement speed GPS/location accuracy stationary devices iOS terminating/suspending the application force-quitting the application from the App Switcher large/small geofence radius multiple monitored regions Is it possible to use significant-change location updates + region monitoring together for this type of attendance workflow? For an enterprise application where the user explicitly grants Always Allow Location permission and Precise Location is enabled, what level of reliability can realistically be expected from iOS geofencing? Important business constraint We cannot require employees to manually open the application every time they arrive at or leave the workplace. The objective is an automatic attendance system, where the employee's entry and exit from the workplace geofence is detected by iOS and the application records the corresponding attendance event. We understand that iOS is designed to protect battery life and user privacy and that continuous background execution may not be permitted. We are therefore looking for the Apple-recommended architecture for achieving this requirement using supported iOS APIs, rather than trying to circumvent iOS background execution policies. Any guidance from Apple engineers or developers who have implemented reliable enterprise geofencing would be greatly appreciated.
Replies
1
Boosts
0
Views
559
Activity
3w
CLLocation acquisition time: supported monotonic timestamp or bounded age conversion on iOS 16+?
For an application supporting iOS 16 and later, is there a supported public API that exposes a monotonic timestamp for the original determination of a CLLocation, rather than the time it is delivered to CLLocationManagerDelegate? The requirement is to reject observations whose original acquisition age exceeds 10,000,000,000 ns at the final native transport-dispatch check. Exactly 10 seconds is allowed; 10 seconds plus 1 ns is rejected before conversion to milliseconds. This is an arithmetic boundary requirement, not an assumption that location measurements have nanosecond physical accuracy. CLLocation.timestamp is a Date for when the location was determined. Sampling a continuous monotonic clock in didUpdateLocations instead measures callback receipt. Cached observations, batched updates and delayed background delivery can separate those events. Does a public API provide either: A monotonic acquisition/determination timestamp associated with that same CLLocation; or A documented finite uncertainty bound and supported method for relating its Date timestamp to a sleep-inclusive monotonic clock at dispatch? How do the documented guarantees handle wall-clock adjustments between determination and delivery, device sleep, suspension, queued updates and process restarts? If a newer API supplies stronger evidence, what is its minimum supported iOS version? If neither mechanism is available, is there a supported request or delivery mode that establishes a documented lower bound on the original determination time and can reliably reject older cached observations? A recent callback or request by itself would not establish that relationship. I would appreciate documentation describing the guarantees, limitations or supported alternatives. I have not established that such a mechanism is impossible; this is a capability clarification, not a claim of a reproduced operating-system defect.
Replies
1
Boosts
0
Views
149
Activity
3w
Location Services stopped working across the system on macOS
MacBook Air (M4) Current build: macOS 27 Developer Beta (26A5368g) I have a system-wide Location Services failure affecting Apple Maps, Safari geolocation APIs, and any application requesting the current location. Symptoms: Apple Maps cannot determine current location. Safari and browser geolocation APIs fail. Websites report that location cannot be found. Location Services are enabled and permissions are granted. The issue has persisted across: macOS 26.5 beta macOS 26.6 beta macOS 26.6 beta 2 macOS 27 Developer Beta Troubleshooting already performed: Multiple Wi-Fi networks tested. iPhone hotspot tested. VPN enabled and disabled. Location Services reset. Permissions reset and reauthorized. New clean local user account created (no Apple ID, no third-party software). Issue reproduces identically in the clean account. Technical observations: locationd logs repeatedly show: knownCount = 0 AlsWifi = unknown while Wi-Fi scanning itself appears successful: queryMacAddresses.size = 57 The system sees dozens of nearby access points, but none appear to be recognized for Wi-Fi positioning. Additional findings: Wi-Fi hardware functions normally. Internet connectivity is normal. Bluetooth and Find My device presence work. GeoServices resources are present on disk. No successful location fix is ever produced. Has anyone seen similar CoreLocation / GeoServices behavior where Wi-Fi scans succeed but knownCount always remains 0 and no location fix is generated?
Replies
11
Boosts
2
Views
2.2k
Activity
3w
System-wide Core Location failure on macOS 27.0.1: Wi-Fi positioning knownCount=0, incorrect time zone, same failure on Wi-Fi-only iPad
I am experiencing a system-wide Location Services failure on my MacBook running macOS 27.0.1. Several days after the problem first appeared on the Mac, my iPad Pro (Wi-Fi-only model) developed a very similar issue. Both devices are in Ukraine and should use the Europe/Kyiv time zone. The Mac unexpectedly selected Cupertino, PDT, while the iPad selected a Chinese time zone. Location detection is now failing in Apple Maps, Weather, browsers, and other applications using Core Location. My iPhone continues to determine its location correctly. The macOS locationd diagnostic logs show that Wi-Fi access points are being discovered but none are recognized as known references in the observed positioning check. Steps to reproduce Connect the affected Mac to a working Wi-Fi network with internet access. Ensure Location Services are enabled. Open Apple Maps and request the current location. Attempt browser-based geolocation using a website that requests the current location. Open System Settings → General → Date & Time and enable automatic time-zone detection. Observe the inability to determine the correct location and the incorrect automatic time-zone selection. The failure persists across multiple Wi-Fi networks, including an iPhone Personal Hotspot. Expected result Core Location should correctly determine the approximate physical location in Ukraine using available positioning information. Apple Maps, Weather, browsers, and other applications should receive valid location data. Automatic time-zone detection should select Europe/Kyiv. Actual result Apple Maps cannot correctly determine the current location. Browser geolocation fails. Weather displays incorrect location-dependent information. Automatic time-zone detection selected Cupertino (PDT) on the Mac instead of Europe/Kyiv. The Wi-Fi-only iPad Pro independently selected a Chinese time zone instead of Europe/Kyiv. Automatic location detection remains unusable across applications. The problem persists after connecting to different Wi-Fi networks. The Mac problem began suddenly during normal use. Around that time, the system automatically transitioned to dark appearance for the evening (as expected), but the automatic time zone also changed unexpectedly. The iPad developed similar symptoms several days later. Troubleshooting already performed Tested multiple Wi-Fi networks. Tested internet access through an iPhone Personal Hotspot. Checked IP-based geolocation using external services; these correctly identify the geographic region. Considered VPN-related causes; the behavior is not explained by the IP geolocation results. Confirmed that Location Services work correctly on my iPhone. The simultaneous involvement of two independent devices, combined with normal iPhone positioning, suggests a possible failure in Wi-Fi-based positioning or the associated system services rather than an isolated hardware issue. Technical diagnostics On October 22, 2026, the following message was obtained from the macOS locationd unified log: 2026-10-22 22:31:00.638 Df locationd[387:2755b6] [com.apple.locationd.Position:GeneralCLX] WifiAps, querycheck, knownCount, 0, unknownCount, 17, knownCountTile, 0, knownToUnknownRatio, 0.0, queryMacAddresses.size, 34, sinceLastServerQuery, 187.15, isQueryNeeded, 1, forceQuery, 0, queryType, 0, reqType, 0 Important diagnostic fields: knownCount = 0 unknownCount = 17 knownCountTile = 0 knownToUnknownRatio = 0.0 queryMacAddresses.size = 34 isQueryNeeded = 1 These values indicate that the positioning subsystem is discovering Wi-Fi access points but has no recognized positioning references in this particular check. This resembles a previously reported Core Location / GeoServices failure. Potentially related existing reports Apple Developer Forums: https://developer.apple.com/forums/thread/835896 The discussion documents a similar system-wide location failure with knownCount = 0 despite successful Wi-Fi scanning. Feedback IDs submitted by another affected user: FB23196632 FB23366087 There are also independent reports from Ukrainian users whose Macs incorrectly determine their location or time zone as China: https://www.reddit.com/r/MacOS/comments/1nt0lli/location_glitch/ These reports may involve the same underlying issue, but a common root cause has not been confirmed. Request for investigation Please investigate whether this issue is related to: Apple's Wi-Fi positioning database or lookup service. Core Location / GeoServices processing of Wi-Fi-based location results. Incorrect, missing, or stale Wi-Fi access-point location records. Local positioning cache or Wi-Fi regulatory-domain problems. I would particularly appreciate investigation of the knownCount = 0 condition and whether it can explain the incorrect time-zone selection on two separate devices. Please route this report to the appropriate macOS Core Location / GeoServices engineering team. I can provide additional diagnostic logs and sysdiagnose data if required.
Replies
1
Boosts
0
Views
960
Activity
4w
How to pass off liveUpdates(_:) to main app
Hello! I was looking through Apple's documentation about Core Location and the Location Push Service Extension, and it seems like you can 'pass-off' liveUpdates(_:) to the main app (yes, that's simplified), but they don't seem to explain what that means, and any way on how to do it. Do they just mean like a SLC, or silent push? I am just curious, because it isn't clear at all what they mean. Thanks!
Replies
1
Boosts
0
Views
199
Activity
Oct ’26
GPS not working after iPadOS 27 upgrade on iPad Cellular Gen 9
There is a post out on the main community page (https://discussions.apple.com/thread/256371563?answerId=262162384022&sortBy=rank#262162384022) that discusses several users with issues around the GPS not working after the iPadOS 27 update on Gen 9 iPads. I also ran into this. I did everything mentioned in the community post (including completely wiping my iPad) and nothing worked. However, I did try updating to 27.2 Beta 4 and it seems to have fixed the issue. Is there a specific fix for the GPS not working on an iPad Gen 9 after upgrading to iPadOS 27 in 27.2? I'm thrilled it is working again, but wondering if it's just a fluke or if something really was addressed?
Replies
0
Boosts
1
Views
125
Activity
Oct ’26
Unexpected Immediate Delivery of Multiple UNLocationTrigger Notifications
Hello, I'm encountering an issue with UNLocationNotificationTrigger in my iOS app. I've scheduled three local notifications using UNLocationNotificationTrigger, each tied to a distinct geographic region. These regions are significantly distant from one another and should not trigger simultaneously under normal movement conditions. However, during testing, the user received all three notifications within one second, despite being physically located near only one of the regions. This behavior is unexpected and defeats the purpose of using location-based triggers. Could you please clarify why this might be happening? Is there a known issue with UNLocationTrigger, or is there a possibility that iOS preemptively triggers all scheduled location notifications? Any guidance or recommended practices to avoid this behavior would be greatly appreciated. Thank you!
Replies
6
Boosts
0
Views
997
Activity
Oct ’26
Title Location updates stop or become highly inaccurate during navigation on iOS / iPadOS 27 Body We develop and operate a navigation app. Since updating to iOS / iPadOS 27, several users have reported that location updates stop during navigation,
I'm working on a navigation app. Since updating to iOS / iPadOS 27, several users have reported that location updates stop during navigation, or that the displayed location is far from where they actually are. Some users say the same thing happens in Apple Maps and Google Maps, so the cause seems to be in the OS rather than in any particular app's implementation. Reported symptoms The current location stops updating, or updates intermittently, during navigation The current location is shown far away from the user's actual position Reported devices and OS versions Almost all reports come from the iPad (9th generation), but the issue also occurs on iPhone. iPad (9th generation) Wi-Fi + Cellular / iPadOS 27.0 iPhone 16 Pro Max / iOS 27.0 iPhone 16 Pro / iOS 27.2 Public Beta iPhone 17 / iOS 27.0 Suggested workarounds (none resolved the issue) None of the following steps suggested to users helped: Checking location permissions ("While Using the App" or "Always", with "Precise Location" turned on) Turning Location Services off and on again Restarting the device Using "Reset Location & Privacy" Questions Has anyone else received similar reports on iOS / iPadOS 27? Any app-side workarounds would be greatly appreciated.
Replies
0
Boosts
1
Views
404
Activity
Oct ’26