Share My Location Not Working Diagnosing And Solving Common Failures

Why location sharing breaks and how to fix it

Location services are one of those features that work perfectly until they don't. I spend most of my week troubleshooting this for people who've already tried restarting their phone and asking their kid if they're "too far away." The problem is almost never what they think it is. Before you dig into settings, there's a basic distinction that saves about twenty minutes of troubleshooting right there. Location sharing is not the same thing as location services being enabled. You can have all the right permissions set up and still never see anyone's dot on the map because the underlying GPS stack is stuck in a low-power state that nobody bothers checking. On iOS, which is where I deal with this most, Apple uses a system called Geofencing combined with GPS, Wi-Fi triangulation, and cellular tower positioning. The device doesn't constantly ping satellites. It hibernates between updates, waking only when it detects significant movement or when an app explicitly requests a location fix. When it doesn't wake properly, you get stale data. The person sharing appears frozen at their home from three hours ago.

Here's the counter-intuitive part most people miss. Turning location services back on doesn't always fix a stuck geofence. I had a customer last month whose daughter's location was frozen at the school gate for four straight days. She'd restarted her iPhone six times. She'd toggled location services on and off. The real issue was the Find My network's background refresh had been quarantined by a battery optimization update that iOS pushed silently in the middle of the night. Going into Settings > Privacy & Security > Location Services > Find My and switching between "While Using" and "Always" forced the system to re-register the geofence. That's the move nobody tells you about. Android has a completely different failure mode. The Google Play Services location cache corrupts far more often than the average user realizes. I see it maybe twice a week. Someone shares their location through Google Maps and it shows "Location not available" even though they can open Maps and navigate fine. The navigation works because the GPS chip is functional, but the background location API that other apps and services depend on is broken. Clearing the cache for Google Play Services usually resolves it in under a minute. Settings > Apps > Google Play Services > Storage > Clear Cache. That's it. Another thing people get wrong is assuming the person on the other end has a connectivity problem. Sometimes it's their phone, sometimes it's yours, and sometimes it's the server side. iMessage and Google's location sharing both route through Apple's and Google's respective servers. If those servers are having issues, which happens a few times a year without much announcement, nothing you do on either device will fix it. Check downdetector or the Apple Support Communities. If three thousand other people are reporting the same thing on a Tuesday afternoon, your troubleshooting is wasted time.

There's also the bandwidth issue that nobody considers. Location sharing over cellular can fail silently on networks with poor upstream capacity. The GPS coordinates are tiny data, but the handshake protocols around authentication and encryption take more round trips than people expect. I had a situation where a mother couldn't see her son's location while he was on 4G in a rural area, but the moment he connected to his school's Wi-Fi, his dot appeared instantly. Switching the network environment was the actual fix, not any settings change. If you're sharing between iOS and Android, be aware that Apple's Find My and Google's location sharing use different protocols entirely. They don't interoperate natively. You need a third-party app like Life360 or Glympse, and those introduce their own failure modes. Life360's location polling depends on its own background refresh permissions, which manufacturers love to strip away. Samsung phones in particular will kill the app's background activity unless you explicitly whitelist it in the battery settings. Without that whitelist, you're looking at location updates that are anywhere from five to forty-five minutes old. The Bluetooth proximity feature in Find My works differently and trips people up. It doesn't use GPS at all. It broadcasts a rotating identifier that nearby Apple devices pick up and relay back through the Find My network. If someone says their shared location shows "No Location Available" and they're sitting in their living room, this is usually why. There are no other Apple devices within range to act as relays. Moving to a populated area or enabling "Find My network" in settings so your own device can report its position to itself fixes this about half the time.

One last thing that causes legitimate confusion. Time zones. I once spent two hours troubleshooting a frozen location for a guy whose family was spread across three time zones. His phone was showing the correct time, but the location sharing server had cached an old timestamp and was serving stale data because daylight saving time transitions had desynced the session. A full logout and re-login to the Apple ID on the sharing device resolved it. Not a settings toggle. A full sign out and back in. The bottom line is that most failures fall into three buckets: the device's location stack got stuck and needs a forced re-register, the network path between the two devices has a bottleneck, or the servers themselves are the problem. Start by checking the second option because it's the easiest to verify, then move to the re-register step, and only then consider whether it's a server outage. That sequence saves more time than any other approach I've seen.