Family Link Not Working: Root Causes, Step-by-Step Fixes, and a Reliable Alternative

If you landed here, Family Link probably stopped doing the one thing you set it up to do — your kid blew past Downtime, the map shows a location from two hours ago, the parent access code keeps getting rejected, or the install request you were promised never pinged your phone. „Family link not working“ is rarely one bug; it is four or five different failure modes that look identical on the surface. This guide takes a symptom-first approach: match what you are seeing to the right section, run the targeted fix in order, and skip the generic „reboot everything“ advice that wastes an afternoon. If the fix still does not stick, there is a credible alternative section at the end that covers the same parental jobs without the same brittleness. For the broader app-blocking strategy Family Link sits inside, our guide on how to block social media on your phone walks through every layer you can stack with it.

Why Family Link Breaks: The Four Failure Modes Parents Actually Hit

Most „google family link not working“ reports collapse into four distinct categories, and the fix for each is different. Knowing which category you are in saves you from reinstalling everything in frustration.

• Limits do not enforce. Downtime ends but the phone stays locked, or the daily limit passes and the app keeps running.
• Location is stale. The child marker on the map is hours, not minutes, old.
• Parent access code is rejected. You type the code, the child device shrugs.
• Approval requests vanish. Your child taps „ask parent,“ but your phone never buzzes.

Family Link supervision is a background service on the child device, and it depends on three quiet things staying healthy: Google Play Services being current, battery optimization leaving it alone, and the supervised Google account staying signed in. When any of those drifts, supervision degrades silently — no error toast, no banner, just rules that quietly fail.

Use this guide by jumping to your symptom, running the targeted fixes in order, and only escalating to a reinstall or alternative if the targeted fix does not hold. And before you spend three hours debugging, sanity-check that your setup was actually supported in the first place — an iPhone child, a web-only parent, or an older Chromebook all have real platform limits that no troubleshooting can remove.

Fix 1: Downtime and Daily Screen Time Limits Not Enforcing

„Family link screen time not working“ and „family link downtime not working“ are the most-reported failures, and there are four root causes that look identical from the parent dashboard. On the iOS side, Screen Time limits that won't stick has its own equivalent root-cause list.

Root cause A — Play Services version mismatch. After an Android system update on either device, Google Play Services and the Family Link app can fall out of sync, and the child device stops honoring server-pushed rules.

• Open the Play Store on both the parent and child device.
• Update Google Play Services and the Family Link app (parent app on your phone, the child-side companion on theirs).
• Restart both devices once updates finish.

Root cause B — battery optimization killing supervision. Android's Adaptive Battery and aggressive vendor power managers (Samsung, Xiaomi, OPPO) will put the supervision service to sleep, and limits stop firing.

1. On the child device, open Settings → Apps → Family Link → Battery.
2. Set battery use to Unrestricted.
3. Repeat the same setting for Google Play Services.
4. On Samsung devices, also remove both apps from „Deep Sleeping apps“ under Device Care.

Root cause C — clock or timezone drift. Downtime windows evaluate against the child device's local clock. If that clock is wrong, the window opens and closes at the wrong moments.

• Settings → System → Date & time → set Automatic date & time and Automatic time zone to on, on both devices.

Root cause D — category limit but the app is not categorized. Daily limits set at the category level (Games, Social) only cover apps Google has classified into that category. A sideloaded or miscategorized app slips through.

• In the parent app, open the child profile → App limits → tap the specific app → set an individual daily limit.

After applying a fix, do not trust the dashboard — verify on the child device. Force-stop the supervised app, reopen it, and confirm the lockdown screen actually appears at the time it should.

Fix 2: Location Not Updating or Showing as Stale

„Family link location not updating“ almost always traces back to three culprits: battery optimization, downgraded permissions, or no connectivity. Family Link does not pull location actively from the parent side — the child device pushes it, and anything that throttles background work on that device throttles your map.

• Battery saver and Adaptive Battery. Both deprioritize background apps, including Family Link's location reporting. Disable battery saver and exempt Family Link from Adaptive Battery on the child device.
• Permission downgraded to „while using.“ Android 10+ encourages users to drop apps from „Allow all the time“ to „Allow only while using the app.“ Family Link cannot report a background location with the lower setting.
• No Wi-Fi and no cellular data. Family Link cannot push a fresh fix to Google's servers, so the parent app shows the last known position with a stale timestamp.

Fix it in this order on the child device:

1. Settings → Location → App location permissions → Family Link → Allow all the time.
2. Settings → Apps → Family Link → Battery → Unrestricted.
3. Settings → Location → set mode to High accuracy (uses GPS, Wi-Fi, and mobile networks).
4. Confirm the device has either Wi-Fi or mobile data and is not in airplane mode.
5. Open the parent app, pull to refresh, and confirm the timestamp updates within a few minutes.

If the timestamp still does not move after fifteen minutes with the device awake and online, the supervision service itself has likely been killed — sign out and back into the supervised Google account on the child device to wake it up.

Fix 3: Parent Access Code Not Working

„Family link parent access code not working“ is usually not a wrong code — it is a stale code or an offline device. The parent access code is a short-lived, server-validated token, which means a handful of small things invalidate it. The iOS counterpart is the Screen Time passcode; if that is the wall, recover a forgotten Screen Time passcode covers it.

• The code is time-limited and rotates. A code you copied from yesterday's session, or even from twenty minutes ago, may already be expired.
• The child device is offline. The code is validated against Google's servers, so the child phone needs working Wi-Fi or mobile data at the moment you press OK.
• Clock drift on either device. If the parent or child clock is off by more than a couple of minutes, the validation window misses.

Do this in one tight loop:

1. On both devices, set date and time to automatic.
2. Confirm the child device is online (loading a webpage in Chrome is a good check).
3. Open the parent app → Parent access code → wait for a fresh code to render.
4. Type that code into the child device immediately — do not wait, do not switch screens.

If the code still fails after a fresh pull on a confirmed-online device, restart the parent app and re-pull once more before assuming a deeper issue.

Fix 4: Approval Requests Not Showing on the Parent Phone

„Family link approval request not showing“ usually means the request was sent and received — it just got silenced before you saw it. The chain has four weak links, and any one of them breaks the flow.

• Notifications muted for the parent app. Easy to do by accident when you swipe away a notification and tap „turn off.“
• Wrong Google account signed in. If you have multiple Google accounts on your phone, the Family Link parent app may be signed into the one that is not supervising your child.
• Do Not Disturb or Focus mode. If Family Link is not on your priority list, DND will swallow its alerts.
• Stale parent app. An out-of-date Family Link parent app can drop push notifications silently.

Run through the chain in order:

1. Settings → Apps → Family Link (parent) → Notifications → re-enable all categories, especially „Requests.“
2. Open the parent app and confirm the supervising Google account in the top-right matches the account that set up your child's supervision.
3. Settings → Sound → Do Not Disturb → People & apps → add Family Link as an allowed app.
4. Update the parent app from the Play Store or App Store.
5. Ask your child to resend the request — old requests do not always rebroadcast automatically.

Platform-Scope Gotchas: iOS Child, Web Parent, and Chromebook

Some „not working“ reports are not bugs at all — they are platform boundaries that no fix can remove. Spending an afternoon on these is wasted time you could have spent on a tool that actually supports your setup. Some are deliberate locks rather than bugs — like Sign Out being greyed out by restrictions on an iPhone.

• iPhone child devices. Apple controls Screen Time APIs tightly, so Family Link supervision on an iPhone child is fundamentally narrower than on Android. Many Android-style controls — app blocking, install approvals, full activity reporting — either do not apply or behave differently. If your child is on iOS and you assumed full parity, you are not troubleshooting; you are bumping into the platform. A parental-control profile can also block screenshots — the can't-take-screenshot fix explains when that is the cause.
• Web-only parent access. The browser-based view at families.google.com has a narrower feature set than the parent mobile app. Several approvals, content settings, and per-app limits can only be edited from the phone. If a control is missing on the web, check the mobile parent app before assuming it is broken.
• Chromebook sign-in drift. Supervision on a Chromebook requires the child to stay signed into the supervised Google account. If they sign out — sometimes accidentally on a shared device — supervision pauses entirely and silently until they sign back in.
• How to tell the difference. If a feature is documented for Android and broken on Android, it is a bug to fix. If a feature is documented as Android-only and you are trying to use it on iOS, Chromebook, or web, it is a platform limit — and you need either a workaround or a different tool.

Quick-Fix Checklist Before You Give Up

If the targeted fixes above did not hold, run this short reset sequence in order. Stop as soon as supervision works again — you do not need to do all five.

1. Update everything. Update Family Link and Google Play Services on both the parent and child device from the Play Store.
2. Re-authenticate the child. Sign out of the supervised Google account on the child device, then sign back in. This re-binds the supervision service.
3. Strip battery restrictions. Set Family Link, Google Play Services, and Chrome to Unrestricted battery use on the child device.
4. Reboot both devices. A clean reboot clears stuck background services and renews network state.
5. Re-pair as a last resort. In the parent app, stop supervision for the child, then add the child back as a new supervised account. You will lose historical settings, so try this only after the first four steps.

If every fix above keeps failing on the same setup, give try NexSpy a look as a switch — same core jobs, different foundation.

When Family Link Still Won't Behave: NexSpy as a Reliable Alternative

If you have run every fix above twice and supervision is still flaky — or you are on a mixed iPhone/Android household where Family Link is structurally limited — it is reasonable to switch to a tool built for the same jobs but on a different foundation. NexSpy is an all-in-one parental control app for Android 8.0+ and iOS 15+ child devices with one Parent Dashboard that covers the same core jobs Family Link advertises, plus several capabilities Family Link does not offer at all.

Same core jobs, fewer brittle dependencies

The day-one Family Link jobs — screen time, Downtime, app management, content filtering — are all first-class in NexSpy and configured from the same dashboard:

• Per-app daily time limits with automatic lockdown when the limit is reached, so the symptom in Fix 1 (limits silently failing) does not happen the same way.
• Downtime scheduling for school nights, bedtime, study windows, and weekends.
• App and Game Blocker with instant block, scheduled block, and a child request-permission flow.
• Focus Mode that locks every app except the Phone app, with parent-approved early end.
• Website filter with adult, drugs, violence, and gambling categories plus a custom blacklist and allowlist, and a Safe Search filter across Chrome, Edge, Firefox, Opera, Samsung Internet, and Safari.

Location that does not go stale

The Fix 2 symptom — a map that lies about where your kid is — is replaced by real-time location and route history of up to 30 days using GPS and Wi-Fi, plus geofencing with virtual safe zones and arrival or departure alerts. Both work on Android 8.0+ and iOS 15+ child devices, so a mixed-device household sees the same map either way.

Safety capabilities Family Link does not offer

This is where the comparison stops being about reliability and starts being about scope:

• SOS Emergency Alerts with a 5-second confirmation countdown, a loud siren that bypasses silent and Do Not Disturb, real-time location, and 15 seconds of surrounding audio.
• Inappropriate Image Detection that scans the entire photo gallery using a machine-learning NSFW model on Android and iOS.
• Daily and Weekly Activity Reports with screen time, top apps, app categories and age ratings, notification frequency, and a 30-day lookback.
• Family Chat inside the Parent Dashboard for parent-child messaging.

When NexSpy is the right call: mixed iPhone/Android households, parents who want safety features (SOS, image detection, geofence) on top of screen time, and anyone whose Family Link supervision keeps quietly breaking. When Family Link is still fine: a single Android child, a parent who only needs basic Downtime and install approvals, and a household already deep in the Google ecosystem with no reliability complaints. No rooting or jailbreaking is required either way.