When a setting stops working: a safe check

A parent comes to this page with one job: make sure the rule is still the rule.

One question drives the page: the limit does not apply, the app is back, the report is wrong, the block is bypassed.

What now?

The first instinct is to suspect the child. That is rarely the answer.

Independent testing reports that even the best iOS controls have “confusing setup” and “intermittent glitches” [source: wirecutter-parental-controls].

The Wall Street Journal reported in 2023 that Apple acknowledged a bug in which remotely set restrictions did not stick.

That is historical evidence, not evidence the defect persists in iOS 26. But it is a reason to re-check after every major update [source: wsj-screen-time-bug].

The most common reason a setting “stops working”: the configuration was never fully turned on. Or it was never locked. Or it applies to a different account. Or it was reset by an update. Or it lives on a different device.

This page is a diagnostic order, not an interrogation script.

Work through it calmly.

The order is from most likely to least likely. It runs from “the rule was never set up right” to “the rule was actively defeated”.

If the answer is not on this page, the last section tells you where to look next.

Why this matters

A “stopped working” report almost always has one of three shapes: the limit does not apply, the app or content is reachable again, or the report numbers look wrong.

The first instinct in each case is to suspect the child.

The diagnostic evidence in this wiki says otherwise.

The most common cause across every category is configuration, not circumvention.

The published research in RAW/research/a-ios-controls.md is explicit.

Independent testing found Screen Time setup “confusing”. Reports tell of settings not persisting after an iOS update.

Apple’s regional child-account thresholds differ by country.

Under 14 in Austria, under 16 in Germany, under 13 in Switzerland and most other countries [source: apple-region-rules].

A setting that worked yesterday can quietly fall out of scope the day a child turns 13 in CH, 14 in AT, or 16 in DE.

The order on this page reflects that.

We start with “is the setting actually on, on this account, and locked”.

This is the cluster of cases that account for the largest share of “stopped working” reports in the trick database.

Only after the configuration is sound do we consider update behaviour, device inventory, network scope, account changes, and finally active circumvention.

A diagnostic article that begins with “your child has probably done X” is, in editorial terms, a failure mode.

It sees a problem where most often there is none [source: ADR-0005].

Start here — pick the symptom you are seeing

If you already know what looks wrong, jump to the matching step in the Steps section below.

If two or three of these fit, start at the lowest-numbered step that fits. The order is calibrated to the most common cause first.

If none of these fits, the section If nothing here fits at the bottom tells you where to look next.

Prerequisites

You will need four things in front of you, and a calm moment that is not a confrontation.

• The child’s iPhone or iPad, signed in to the Apple Account that is part of your Family Sharing group.

  The family-management view lives on the family organiser’s device, not the child’s.

  The child’s device is what shows whether a rule is actually in effect [source: apple-family-sharing].

• The family organiser’s Apple Account and its credentials.

  Resetting a passcode or re-applying a setting is done on the organiser’s device, with the Apple Account that was entered at setup [source: apple-passcode-recovery].

• The Screen Time passcode, if one is set, and the device passcode.

  You need a clear sense of whether the two are the same.

  If the Screen Time passcode equals the device passcode, a child who can unlock the device can change the limits [source: apple-screen-time].

• Time and a quiet hour.

  Turning this into an interrogation defeats the purpose.

  The configuration walk is a review, not a verdict.

Verified against iOS 26.1, checked 2026-08-19 [source: apple-screen-time].

If the device is on a different iOS version, the menu labels may differ [source: apple-user-guide-screen-time].

Steps

The diagnostic order is calibrated to the most common cause first and the least common last.

Each step is a verification, not a workaround.

If the first step solves it, you are done.

If not, the next step is informed by what the first one told you.

1. Is the setting actually on, on this account, and locked?

   This is the largest cluster of “stopped working” reports in the trick database, and the cheapest to verify.

   Before looking at the symptom, confirm the rule is still a rule.

   Open Screen Time on the family organiser’s device and check, in this order:

   • Screen Time is on and the device is set as a child device. Without this, nothing else applies [source: apple-screen-time].

   • “Lock Screen Time Settings” is on, and the Screen Time passcode differs from the device passcode.

     Apple documents that a Screen Time passcode that matches the device passcode leaves the limits changeable by anyone who can unlock the phone [source: apple-screen-time].

   • Content & Privacy Restrictions is on.

     This is the container that holds purchases, content, app installation, and privacy changes.

     The dedicated Apple support page names it Beschränkungen in German and “Content & Privacy Restrictions” in English [source: apple-parental-controls].

   • Each rule you remember setting is still toggled on.

     The App Store, the explicit content rating, the web content level, the iTunes & App Store Purchases block for in-app purchases, the privacy-change lock, the account-change lock [source: apple-parental-controls].

   • For an under-13 child account, the Screen Time passcode gate before viewing detected sensitive content is in place.

     Apple documents that this gate begins in iOS 18 [source: apple-communication-safety].

   If the child has a separate, second Apple Account they signed in to on the same device, the configuration on the family-organiser view is not the configuration that controls what that account sees.

   Apple describes the family membership model in [source: apple-family-sharing] and the child-account creation in [source: apple-child-account].

   A second account is treated in Step 3.

2. Did an iOS update reset it?

   iOS updates can change default values for settings that the family had previously turned off.

   They can also add new toggles that default to a less restrictive state.

   Three documented cases:

   • Screen Distance is enabled by default for an under-13 child in Family Sharing.

     It is re-enabled for all of that child’s devices when the child updates a signed-in device [source: apple-screen-distance].

     A child who was in the habit of holding the phone close may have been “switched on” by an update.

   • App Store, account-change and privacy rules can be returned to default after a major update.

     Re-check the Content & Privacy Restrictions container after every iOS major release [source: apple-parental-controls].

   • In the EU, alternative app marketplaces exist as a separate setting inside Content & Privacy Restrictions.

     An iOS update can re-open this switch.

     Apple states that for purchases outside the App Store / Apple In-App Purchase path, Ask to Buy, purchase sharing and Screen Time in-app-purchase restrictions do not apply [source: apple-alt-app-distribution] [source: apple-alt-app-restrictions].

   If the rule stopped working the day after an update, this is where to look first.

3. Is this the device and the account the child is actually using?

   A rule set on the family-organiser’s iPhone does not, by itself, cover the iPad in the kitchen, the laptop in the study, the friend’s phone, the school device, the console in the living room, or a sibling’s hand-me-down tablet.

   Apple documents the Family Sharing device scope in [source: apple-family-sharing] and the regional age-driven transition from a managed child account to a self-managed one in [source: apple-region-rules].

   For an under-13 child in CH, under-14 in AT, or under-16 in DE, the rules apply automatically. Once the threshold is crossed, the account moves.

   For each device the child touches in a normal week, ask:

   • Whose Apple Account is signed in?

     A child signed in to a parent’s account sees the parent’s setup, not the child’s.

     A child signed in to a second, unmanaged Apple Account sees no family-managed restrictions at all.

   • Is the device in Find My, with the family-organiser Apple Account as the iCloud account?

     A device that has been factory-reset or returned to setup will accept a new Apple Account.

     The family configuration will be gone [source: apple-family-kids].

   • Is the Screen Time “this is my child’s iPhone” setting still on this device?

     If it was ever turned off and the device is now treated as a parent or adult device, the limits do not apply [source: apple-screen-time].

   If a device is in the picture that you did not know about, configure it.

   No consumer Screen Time path covers cross-platform.

   A Mac, a Windows PC, a Chromebook, a Nintendo Switch, a PlayStation, an Xbox, a smart TV, or a school-managed iPad each have their own controls.

   A setting on the iPhone does not reach them [source: apple-family-sharing].

   The Apple Platform Deployment Guide covers organisation-managed devices and is not the same path as a consumer Screen Time setup [source: apple-deployment-restrictions].

4. Is the rule on the right network or the right plan?

   Settings that work at home can fail outside the home — by design, not by bypass.

   • Mobile data is not filtered by a home router rule.

     A rule that worked on the home Wi-Fi does not follow the device onto cellular.

   • Public Wi-Fi and hotspots are outside any home-network rule.

     A friend whose phone shares its hotspot is, from the device’s point of view, an unmanaged network.

   • VPN, custom DNS, or DNS-over-HTTPS on the device defeats network-layer filters without doing anything to the on-device Screen Time settings.

     The Screen Time report and limits still apply.

     The web filter that runs on the router does not.

   Apple’s family-management view is at the Apple Account and the device, not at the network [source: apple-family-sharing].

   If the issue is “the page loads at school but not at home” or “the page loads on the bus but not on the home Wi-Fi”, this is the layer that explains it.

   The on-device settings are still in effect.

   The network filter is not.

5. Is the limit, the downtime, or the report itself the broken piece?

   If the symptom is “the child uses the device during downtime” or “the Screen Time report looks wrong”, the configuration in Step 1 may be correct and the limit or report is the thing behaving unexpectedly.

   • “One more minute” prompt: a child can ask for additional time against an App Limit.

     A parent can approve or deny.

     This is documented Apple behaviour, not a failure [source: apple-screen-time].

   • Siri, widgets, notification replies, and the web version of a limited app: each can be used during Downtime if it lives outside the Downtime block.

     Verify Always Allowed and the per-app block [source: apple-screen-time].

   • App deletion and re-installation: if App & Website Activity is on, deleting an app and reinstalling it can reset the limit clock for that app.

     The configuration is correct.

     The behaviour is the design [source: apple-screen-time].

   • Airplane mode or offline use: a device on a schedule that goes into Airplane mode near a limit boundary can show a confusing report on the next online sync.

     This is a display lag, not a setting failure [source: apple-user-guide-screen-time].

   • One daily Downtime schedule: Wirecutter’s 2026 test notes that Screen Time permits only one daily Downtime schedule.

     Weekend and weekday schedules are not separate [source: wirecutter-parental-controls].

     If you were expecting two schedules, the configuration is not the one you remember.

   If the report numbers are still off after this step, the most common reason is that App & Website Activity is not enabled on the child device.

   Without it, the report is incomplete by design [source: apple-screen-time].

6. Is the page or app still reachable through an in-scope gap?

   If a single page, app, or content type is the trigger, the rule may be in force but the content is reaching the child through a different surface.

   • The blocked app’s website is not covered by an App Limits rule that names the app.

     A web rule on the same content requires a separate Web Content setting [source: apple-parental-controls].

   • An alternate browser is not covered by a Web Content rule that names one browser.

     The iOS Web Content Filter covers Safari and apps that use the iOS WebKit surface.

     Coverage in third-party browsers and embedded web views is not established by Apple’s consumer support pages [source: apple-parental-controls].

   • Siri or assistant web search can fetch a page that the Web Content filter would have blocked [source: apple-screen-time].

   • DNS-over-HTTPS, alternate DNS resolvers and HTTPS web proxies can route a request around a network-layer filter without affecting on-device settings.

   • Signed-out YouTube and YouTube via a non-Google search engine are reachable even when SafeSearch is on.

     The rule names one account and one engine [source: apple-screen-time].

   If a single surface is the trigger, the configuration is likely right.

   The rule is just not the rule that covers that surface.

7. Is the spend the trigger?

   If a transaction completed without an approval request, the configuration may still be correct.

   Apple documents that Ask to Buy does not request approval for a child’s own redownload, an app update, or a redemption code [source: apple-ask-en].

   A “purchase” that bypassed approval is, in a meaningful share of cases, one of those three by design.

   If the trigger is a real first-time purchase, check:

   • Ask to Buy is on for this child under the family view.

     The family organiser can see the toggle in the family settings [source: apple-ask-en].

   • The family payment method is the one in use.

     A child who has another payment method on file can complete a purchase that does not touch the family method [source: apple-ask-en].

   • In-app purchases are blocked at the device level.

     This is a separate switch under Content & Privacy Restrictions [source: apple-parental-controls].

   • For subscriptions and recurring charges, the family payment method is the right one to confirm, not the App Store one-off rule [source: apple-ask-en].

   If the spending is in a third-party app — Roblox, Fortnite, Discord — the device-level Screen Time rule does not cover in-app purchases inside that app.

   Each platform has its own parental controls, and a setting on the iPhone does not reach them.

8. Has the operating system itself been modified?

   Only after Steps 1–7 fail.

   The cases here are real but rare, and the configuration walk has ruled out the more common ones.

   The signals worth checking:

   • A banking or security app warns about device integrity.

     Modern iOS apps will not run on a jailbroken device, and the warning text names the cause.

   • A package-manager app such as Cydia or Sileo appears on the home screen.

     A package manager app on a stock iPhone is a strong signal of jailbreak.

   • Developer mode is on, or the device shows the Xcode developer image.

     This is a developer setting that, on a child’s daily-use device, is unusual.

   • A factory reset or DFU restore was performed.

     Apple documents that Activation Lock, when correctly bound to the family-organiser Apple Account, prevents a stranger from using a reset device.

     Find My is the recovery path [source: apple-family-kids] [source: apple-user-guide-screen-time].

   If any of these is true, the configuration on the iPhone is no longer authoritative.

   The right next step is to recover the device through the family organiser, not to reapply a rule on it.

9. Is a social or relationship layer at work?

   Run this step in parallel with the others.

   A setting that “stopped working” can be the surface of a conversation that the family has not had, not a configuration gap.

   • Repeated exception requests, with a child asking the same parent on the same day, can be a sign that the rule no longer fits the situation, not a sign of technical failure [source: apple-screen-time].

   • An “emergency” or “for school” framing of a request is a real category, and is worth a calm check rather than an automatic yes or no.

     Apple documents that a child can request more time against an App Limit, and a parent can review and decide [source: apple-screen-time].

   • Two caregivers giving different answers to the same request is not a setting failure. It is a coordination gap.

     The configuration on the iPhone will reflect whichever decision was last synced.

   • Notification previews on the family organiser’s lock screen can show content the child sent or received.

     If this is a surprise, the preview setting on the organiser’s device is the configuration to change, not the child’s [source: apple-screen-time].

   The Talking about it section below treats the conversational layer at length.

What each result means

Each step’s outcome points to a different fix.

The point of the diagnostic order is to know which one you are in.

• Step 1 turns up a setting that is off, or never locked, or that the family has forgotten to apply on the new device.

  The fix is configuration: turn the rule on, lock the settings, set the Screen Time passcode, and verify the rule on the child device.

  This is, by a wide margin, the most common fix and the one the diagnostic order is built around [source: apple-screen-time].

• Step 2 turns up an iOS update that reset a default.

  The fix is also configuration: re-toggle the rule, set it again on every device the child uses, and remember to repeat after the next major update [source: apple-parental-controls] [source: apple-screen-distance].

• Step 3 turns up a device the child uses that is not in the family inventory, or a different account on the same device.

  The fix is inventory: bring the device under the family configuration, or accept that the rule does not reach it [source: apple-family-sharing].

• Step 4 turns up a network where the rule does not apply.

  The fix is at the right layer: on-device settings for content and time, network settings only for the network that the device is on [source: apple-family-sharing].

• Step 5 turns up a limit, downtime schedule or report that is behaving as designed but the design was not what you remembered.

  The fix is either a re-read of the documented behaviour, or a renegotiation of the rule with the child [source: apple-screen-time] [source: wirecutter-parental-controls].

• Step 6 turns up a content surface that the rule does not cover.

  The fix is a rule for the surface, not a stronger version of the same rule on the wrong surface [source: apple-parental-controls].

• Step 7 turns up a purchase that the design does not require approval for, or a third-party app where the iPhone rule does not apply.

  The fix is at the app or payment level, not on the iPhone [source: apple-ask-en].

• Step 8 turns up a device-integrity signal.

  The fix is recovery, not configuration: re-bind the device through the family organiser and verify Activation Lock and Find My [source: apple-family-kids].

• Step 9 turns up a conversational or coordination gap.

  The fix is the next section, not a setting [source: apple-screen-time].

If two steps both turn up something, fix the lower-numbered one first.

The order is not arbitrary.

It is calibrated to the most common cause first, and the rare cause last.

If nothing here fits

A few cases fall outside the diagnostic path above.

None of them is a reason to escalate the configuration.

Each has its own next step.

• The child has crossed the regional age threshold for a child Apple Account.

  In Austria the threshold is under 14, in Germany under 16, in Switzerland and most other countries under 13 [source: apple-region-rules].

  When the threshold is crossed, the account transitions automatically, and some controls move to the child’s own consent.

  The right next step is a conversation about the transition, not a re-application of the rule.

• The setting works on the iPhone but not on a Mac, a PC, a Chromebook, a console or a smart TV.

  The Apple family configuration does not reach those device classes.

  Each has its own controls [source: apple-deployment-restrictions].

  Treat the configuration walk as iPhone-only.

• The setting works on the iPhone but not on a friend’s device, a school device or a borrowed device.

  The configuration does not follow the child to a device the family does not manage.

  The right next step is to talk to the other household, not to tighten the home configuration.

• The child has asked to leave Family Sharing, or has done so.

  Apple documents the leave-from-Family flow for a child in the family, and the parental account-change lock as the relevant countermeasure while the child is still in the group [source: apple-family-kids] [source: apple-parental-controls].

  If the leave has already happened, the configuration on the iPhone is no longer authoritative.

• The rule is being argued about more than configured.

  The configuration is not the bottleneck.

  The relational section below is the next step.

• The configuration has been checked against this page and is correct, and the report still does not match what you see.

  Treat the report as a signal to do a calm review, not as evidence of a bypass.

  Wirecutter’s 2026 test reports that Screen Time shows “intermittent glitches” and “limited third-party app control” even on a fully configured device [source: wirecutter-parental-controls].

  The 2023 WSJ report of settings not sticking is retained here as historical evidence only [source: wsj-screen-time-bug].

  Both are reasons to set the next review, not the next alarm.

If the case is none of these, the next step is to write down the date, the iOS version, the steps you took, and the screen you saw.

That is the input the trick database needs to record a new case.

It is the starting point of the next research run.

Talking about it

This section is the longest in the article for a reason.

A “stopped working” report is, in a meaningful share of cases, the surface of a conversation that the family has not had.

The configuration walk above is necessary. It is not sufficient.

The editorial stance of this wiki is that every technical answer carries a relational answer with it.

For the diagnostic article, the relational layer is at least as important as the configuration.

Frame the walk as a review, not an interrogation

A calm configuration review produces better answers than a confrontation.

A child who is being asked to explain why a setting “stopped working” will, in most cases, produce a worse story than the configuration itself.

The independent evidence on this is consistent.

Wirecutter’s 2026 test found Screen Time setup “confusing” — that description extends to the child too [source: wirecutter-parental-controls].

A child who broke a rule may not have been able to interpret the prompt.

The fault may be in the configuration, not in the child.

Walk the configuration together, with the child present, in the order above.

The walk is a normal habit, like a smoke-detector battery check, not a verdict.

What the configuration gap often signals

A “stopped working” report is rarely a signal of concealment.

It is more often a signal of one of three things, each of which has a different next step.

• The configuration was never complete. A setting was on for one account and not the other, or was set on the iPhone and not the iPad, or was set before an iOS update and never re-applied.

  The next step is the configuration walk.

• The child has grown into a device, an account or a social context the family has not configured for.

  A new phone, a new school year, a friend’s device, a console in the living room.

  The next step is inventory.

• The rule is the wrong rule for the situation. A bedtime Downtime that does not accommodate homework, a content filter that blocks a research paper, a purchase block that catches a birthday gift.

  The next step is renegotiation, not re-application.

In all three cases, the question to ask is “what is the rule trying to do”, not “what did the child do”.

The first question is technical. The second is relational. Both matter, and the second cannot be answered by a configuration screen.

If the child says the rule is unfair or outdated

The evidence base for parental controls supports a developmental combination of structure, co-use, discussion, and proportionate safeguards.

Not surveillance or restriction alone.

For younger children, structure and supervision. For school children, clear boundaries plus competence building. For teenagers, proportionate and openly communicated safeguards rather than hidden surveillance.

Translate the technical configuration into a jointly-held rule the child can repeat in their own words.

If the rule cannot be stated plainly, the configuration is unlikely to be the right one.

The point of a rule that a child can restate in their own words is that the rule survives a moment when the parent is not in the room.

If the rule was broken

Avoid turning routine troubleshooting into an accusation.

Ask jointly which devices are used, and why.

The configuration walk is a chance to update the rule, not to assign blame.

Two unprompted questions to ask, in this order:

• “Which devices did you use this week, and on which account?”

  This is the inventory question.

  The answer is what tells you whether Step 3 is the right place to spend time.

• “Was there a moment this week when the rule got in the way of something you needed?”

  This is the rule-fit question.

  The answer is what tells you whether the rule is the right rule, regardless of who broke it.

A configuration that is in force, on the right device, on the right account, and that the child can state in their own words is the configuration the diagnostic path is trying to find.

A configuration that is none of those is a configuration that needs renegotiation, not reinforcement.

If the family separates or the caregivers disagree

A configuration decision that the family disagrees about is not a configuration failure.

It is a coordination gap, and the technical rule will reflect whichever decision was last synced.

The technical fix is a family conversation, not a tighter passcode.

For an at-a-glance reference, the glossary lists the editorial terms used on this page.

The emergency hotlines page is the right next step if the trigger behind the diagnostic walk is a crisis rather than a configuration.

What this section does not do

It does not tell a parent to spy on a child, to read messages covertly, to track location without consent, or to escalate a single broken rule into a punishment.

The editorial stance in ADR-0005 marks these as out of scope.

The page is a diagnostic walk and a calm review.

The configuration is the start.

The conversation is the substance.

Sources

Each marker resolves to a stub under Wiki/sources/ with the URL, the retrieval date and the licence.

• [source: apple-screen-time] — Apple Support, “Use Screen Time to manage your child’s iPhone or iPad” (link-only).
• [source: apple-parental-controls] — Apple Support, “Use parental controls to manage your child’s iPhone or iPad” (link-only).
• [source: apple-passcode-recovery] — Apple Support, “If you forgot the Screen Time passcode for an iPhone or iPad” (link-only).
• [source: apple-region-rules] — Apple Support, “Region-specific rules for managing an Apple Account” (link-only).
• [source: apple-ask-en] — Apple Support, “Approve what kids buy and download with Ask to Buy” (link-only).
• [source: apple-communication-safety] — Apple Support, “About Communication Safety on your child’s Apple device” (link-only).
• [source: apple-screen-distance] — Apple Support, “What is Screen Distance?” (link-only).
• [source: apple-location-sharing] — Apple Support, “Share your location with your Family Sharing group” (link-only).
• [source: apple-family-sharing] — Apple Support, “How Family Sharing works” (link-only).
• [source: apple-family-kids] — Apple Support, “Family Sharing overview for kids and teens” (link-only).
• [source: apple-user-guide-screen-time] — iPhone User Guide, “Set schedules with Screen Time on iPhone” (link-only).
• [source: apple-child-account] — Apple Support, “Create an Apple Account for your child” (link-only).
• [source: apple-deployment-restrictions] — Apple Platform Deployment Guide, “Device management restrictions for iPhone and iPad devices” (link-only, managed-device context; not a consumer Screen Time path).
• [source: apple-alt-app-distribution] — Apple Support, “About alternative app distribution” (link-only).
• [source: apple-alt-app-restrictions] — Apple Support, “How to help ensure you only install apps from the App Store instead of alternative app distribution” (link-only).
• [source: wirecutter-parental-controls] — Wirecutter / NYT, “The Best Parental Control Apps to Manage Screen Time” (link-only, independent test, 2026-08-14).
• [source: wsj-screen-time-bug] — Wall Street Journal, “Apple Admits to Bug in Screen Time Parental Controls” (abstract-only, historical, 2023-07-29; not evidence of a current defect).