Multiple Macs on our network cannot determine location. Time zone stays on Pacific / Cupertino, Maps spins indefinitely, Find My and Weather also fail. Affects 4 of 5 machines tested.
Environment
MacBook Air M4, pro m4, air m1 and others, macOS Tahoe 26.x, Sequoia and Golden Gate
Mixed managed (Jamf Pro) and unmanaged machines — both affected
Two independent networks tested: office (FortiAP, four SSIDs, none using _nomap) and a residential network
No VPN active, no system extensions loaded
Log evidence
Wi-Fi scanning works; the database lookup returns nothing:
@WifiFlow, aps, in, 24, cleaned, 24, usableAps, 0, maxAge, 5.0
WifiAps, querycheck, knownCount, 0, unknownCount, 24, isQueryNeeded, 1
AlsWifi, query, in, 48, paths, 0, 48, 0, out, 0
@WifiLoc, couldn't determine location
@WifiFlow, outcome, nofix
AlsWifi, seriesComplete, known, 0, unknown, 33
Every scanned access point is unknown to Apple. The radio, the scan, and the query path all function — 24 to 55 APs are found depending on location — but zero resolve.
Ruled out
Location Services enabled, including the "Setting time zone" system service
Wi-Fi powered on and associated (not Ethernet-only); country code correct
curl to gs-loc.apple.com reaches Apple and returns a response
No system extensions loaded (systemextensionsctl list empty)
No configuration profile restricting location or privacy
Firewall is inbound-only (per-app control, stealth mode); cannot affect an outbound query
DNS: overrode corporate resolvers to 8.8.8.8/1.1.1.1, verified applied — no change
No proxy configured (scutil --proxy clean)
Same OS version on working and failing machines
Location Services off → killall locationd → on → reboot
Fresh local user account
Both managed and unmanaged machines affected equally
SSIDs do not use the _nomap opt-out
/var/db/locationd cache is SIP-protected and cannot be cleared
Questions
Have someone ever faced the same problem? What was your solution to it?
Is there any supported way to determine whether a given BSSID is present in Apple's location database?
Our APs have been in place roughly two years in an area with regular iPhone traffic. What prevents an access point from being harvested — do virtual or rotating BSSIDs on enterprise APs with multiple SSIDs per radio break the mapping?
Is there a supported way to force a re-query rather than relying on cached position state?
Still testing: one M5 Pro machine reports the correct zone; capturing its locationd output to compare known counts on the same network at the same time. Will update.