Screen Time app limits not working? A practical fix ladder

If your search is “Screen Time app limits not working,” check the configuration before treating it as an iOS bug. Confirm that App & Website Activity is on, the exact app or category is in the limit, the current day has the expected allowance, and the app is not in Always Allowed. If the problem is Downtime, turn on Block at Downtime. If the number looks wrong, select one device in the activity report because Share Across Devices can combine usage and settings from your iPhone, iPad, and Mac.

Then restart the iPhone, install current iOS and app updates, and rebuild one affected limit. If it still fails, record the device, time, settings, and result before contacting Apple or the third-party app developer. Do not use passcode-removal tools.

Which symptom are you actually seeing?

Screen Time can fail in 3 visibly similar ways: a limit is configured differently than expected, the usage report is showing a different scope, or enforcement does not match the saved rule. Identify the symptom first so one change can test one theory.

Symptom	Check first	Action	What the result tells you
An app opens after the limit	App & Website Activity, selected apps, and Always Allowed	Verify the target and remove it from Always Allowed if appropriate	If the app then stops at the limit, the rule was configured differently than expected
The limit is set to 0 minutes and never fires	The allowance value itself	Set the limit to 1 minute and retest	Several public reports describe a 0-minute limit not enforcing where a 1-minute limit did; treat 0 as untested rather than as the strictest setting
Downtime only dims an app	Block at Downtime	Settings › Screen Time › Downtime › Block at Downtime	Apple says Downtime is only a reminder when this is off
A limit runs out sooner than expected	Share Across Devices and report device	Open the activity report and select the individual device	A combined total can include other signed-in Apple devices
An app you never opened reports its limit reached	Whether the limit covers a category or several apps sharing one allowance	Open the limit and read the full selection, then split it into a single-app limit and retest	One allowance shared across a selection is spent by any member of it, so time in a different app can exhaust it
Usage appears while this iPhone was off	Report device and date	Select this iPhone instead of All Devices, then compare the same period	If the number disappears, it came from report scope; if not, preserve evidence rather than guessing at background activity
A limit disappears or returns on several devices	Shared settings and software versions	Inspect each signed-in device and update them before changing the rule again	Apple says shared limits and schedules sync across devices
You cannot edit a limit	Screen Time passcode or Family role	Use official recovery, or ask the family organiser who manages the child account	The issue is authority, not the timer
A third-party blocker stopped shielding apps	That app’s Screen Time permission, selected apps, and schedule	Open the app and follow its repair or permission flow	Permission and app selection are separate prerequisites

What should you check in the Screen Time settings?

The fastest repair is to walk through the saved rule in order. Menu wording below follows Apple’s current iPhone guide and may move in a future iOS release.

Turn on activity tracking. Open Settings › Screen Time. Tap App & Website Activity and turn it on if it is off. Apple notes that turning this feature off also turns off reporting, Downtime, App Limits, and Always Allowed.
Open the actual limit. Go to Settings › Screen Time › App Limits. Confirm that the limit still exists and is enabled.
Expand the category. If you meant to limit one app, make sure you selected that app rather than assuming its whole category contains it. If several apps or categories share one limit, Apple applies one allowance across that selection.
Check the day. Open the limit and inspect Customize Days. A weekday and weekend may have different allowances.
Check Always Allowed. Apple says apps placed in Always Allowed remain available during Downtime and after time limits are reached. Remove only the apps you genuinely do not need available for emergencies or essential communication.
Check Downtime separately. An App Limit controls accumulated use; Downtime controls a scheduled window. Turn on Block at Downtime if you expect unavailable apps rather than a reminder that can be continued.

Apple’s current Screen Time setup guide explains activity tracking and shared devices, while its schedule guide documents App Limits, Always Allowed, and Block at Downtime.

Two configuration traps Apple’s documentation does not name

Two failures come up repeatedly in public discussion, and neither is described on Apple’s support pages. We have not reproduced either under a controlled test, so treat them as checks to run rather than as established platform defects.

A 0-minute limit may not behave as the strictest limit. In an October 2025 r/ios thread, someone reported setting a limit of 0 minutes and 0 seconds on an app and finding it simply did not stop them. The most practical reply was to set the limit to 1 minute instead, which that commenter said was the only configuration they had got to work. If you have reached for 0 because you want the app fully blocked, set 1 minute and retest before concluding that Screen Time is broken. For a permanent block, Downtime with Block at Downtime enabled, or Content & Privacy Restrictions, is the mechanism designed for that job.

A limit reported as reached on an app you have not opened is usually a selection problem. In a February 2026 r/ios thread, someone described watching an hour of a video app that had no limit, then finding that two other apps — both untouched that day — were locked. Another person in the same thread described a 10-minute limit showing as reached first thing in the morning.

The first thing to check there is unglamorous, and someone in that thread said it plainly: confirm the limit still exists and is enabled at all. The second is the selection. An App Limit applies one allowance across everything inside it, so if the limit covers a category rather than a single app, any app in that category spends the same allowance. Open the limit, read its full selection rather than its name, then rebuild it as a single-app limit and retest.

Why is Screen Time higher than the time you used this iPhone?

The first check is the device selector, not a theory about background activity. With Share Across Devices on, Apple says Screen Time settings, reports, and usage are shared across devices signed in to the same Apple Account.

Open Settings › Screen Time › See All App & Website Activity, then tap Devices and choose this iPhone. Compare the same day or week against All Devices. If the high total remains on the single-device view, take screenshots of the device selector, date, app row, and total; Apple does not publish a general user-facing rule that lets us accurately label unexplained time as background use.

Do not “fix” a report by changing several settings at once. Preserve one example, restart, update iOS, and check the same scope again. A repeatable single-device example is useful to Apple Support; a combined chart without its device scope is not.

Why do limits vanish, reappear, or affect another device?

Share Across Devices makes one Screen Time setup apply across an iPhone, iPad, and Mac on the same Apple Account. When it is on, a change is not necessarily local to the phone in your hand; when it is off, each device keeps separate settings.

Apple’s passcode guidance advises updating devices in a Family Sharing group before changing synced Screen Time settings. Check every signed-in device, confirm whether you want shared or separate limits, and then edit the rule once. We found no current Apple support page that documents a specific update bug responsible for limits vanishing or returning, so the honest diagnostic is to verify sync scope before calling it a glitch.

Why did a third-party limit give you a fresh allowance?

If the limit that failed belongs to a third-party blocker rather than Apple’s own Screen Time, there is a documented explanation that is not a bug at all.

Third-party apps set limits through DeviceActivityEvent, and those thresholds count from the moment the app arms them. Apple’s documentation for the includesPastActivity parameter, added in iOS 17.4, describes exactly this: the flag controls “whether the system takes into account the person’s device activity before your app starts monitoring the event”. Apple’s own example — “if your app calls [monitoring] at 1:30pm with a schedule of 1:00pm to 2:00pm, then this boolean determines whether any activity between 1:00 PM and 1:30 PM will contribute to its threshold.”

In practice that means a “30 minutes a day” rule set at six in the evening can grant a fresh 30 minutes on top of everything already spent, unless the developer opted into counting the past. It is not something you can fix in Settings.

What you can do is test it. Use an app heavily, then set or re-set the third-party limit low, and see whether it triggers immediately or hands you a clean allowance. If it is the second, the limit is behaving as “from now” rather than “today”, and that is worth reporting to the developer rather than to Apple.

What is the safest fix ladder if the rule still does not hold?

Change one layer at a time, starting with the least destructive step.

Close and reopen Settings or the third-party blocker. For a third-party app, Apple recommends closing and reopening an app that is not behaving as expected.
Restart the iPhone. Test the same limit once after restart.
Update the app and iOS. Apple recommends checking the App Store for the app update, then updating iOS if no app update is available. Update all devices that share Screen Time settings.
Delete and rebuild one limit. In Settings › Screen Time › App Limits, swipe left on the affected limit and tap Delete, then add it again with a short test allowance. Delete the limit, not the target app.
Test one app on one device. Temporarily use an individual app rather than a broad category and view that device’s report. This reduces the number of settings involved.
Document the result. Record the iPhone model, iOS version, whether Share Across Devices is on, the selected app, the allowance, when use began, and when the limit appeared.
Escalate to the right owner. Contact Apple Support for the built-in Screen Time feature. For a third-party blocker, send the same evidence to its developer after confirming permission and app selection inside that app.

Use a reproducible report rather than “it did not work”:

Device and iOS: ______________________
Apple Account role: self / family organiser / child
Share Across Devices: on / off
Rule and selected app/category: ______
Expected boundary: ___________________
Actual result and exact time: _________
Restarted and retested: yes / no
Screenshots or screen recording: ______

Apple’s general app troubleshooting order is close/reopen, restart, update, and then consider redownloading. Redownloading is deliberately not our first Screen Time step because it can remove a third-party app’s local configuration.

Can a device owner make Screen Time impossible to override?

No self-managed Screen Time setup is impossible for the device owner to change. Apple documents how to delete App Limits, turn off App & Website Activity, and change or remove a Screen Time passcode.

The most-read illustration of this is old but instructive. In September 2018, shortly after iOS 12 shipped Screen Time, an r/apple post titled “My kid managed to pass Screen time limit” reached roughly 9,000 upvotes. The method was not a jailbreak: the child deleted a blocked game, then re-downloaded it from the App Store’s cloud icon, and the freshly installed copy ran without the limit. The parent’s follow-up is the part that matters, and it was upvoted about 1,600 times — they had already restricted the App Store, but previously purchased apps could be reinstalled without new permission, so the route stayed open.

That specific behaviour is from 2018 and we have not retested it; do not assume it still works on current iOS. The durable lesson is the one a commenter in that thread drew at the time: Screen Time behaves as a deliberate obstacle rather than a sealed door. Any system whose keys belong to the person it constrains is a speed bump by construction.

A passcode still adds useful friction. If 2 consenting adults want one person to hold the code for the other, agree on what can be changed, keep Screen Time Passcode Recovery tied to the device owner’s Apple Account, and never share Apple Account credentials. This is a voluntary arrangement, not tamper-proof control.

People who want more than that generally reach for one of two documented routes, both described in a long-running r/nosurf guide to blocking apps on iPhone: setting a Screen Time passcode so that a third-party blocker’s own “allow” path cannot be taken without it, and supervising the device, which unlocks stricter configuration but requires erasing and setting up the iPhone again. Both raise the cost of an override. Neither removes the owner’s ultimate control, and supervision in particular is a significant step to take on a personal phone.

A third-party app can add stricter workflows or make an override visible to somebody else, but it still depends on Screen Time permission that the device owner can revoke. Be wary of any product that promises an unbreakable lock on an iPhone you own.

How does Scrollmates surface a broken Screen Time dependency?

Scrollmates treats missing Screen Time permission and a missing block list as 2 different repairs. Its local policy puts permission first because the Apple app picker cannot provide a usable selection without approval; the app refreshes permission when it returns to the foreground and tells the person when minutes are not counting or shields are not running.

On 23 August 2026, we ran the 15 targeted RepairCardTests on an iPhone 17 Pro simulator using iOS 26.5; every test passed. They cover permission and orphaned-list policy, denied-permission copy, light and dark rendering, both repair surfaces, and foreground re-evaluation. This verifies Scrollmates’ current repair-state logic and UI, not whether Apple will always deliver a Screen Time event on physical hardware.

That does not make Apple’s frameworks exact or impossible to disable. Scrollmates is not for Android, parental control, or anyone who needs a hard lock; it is an iPhone accountability system where 2 people share one daily pool, and a claimed session or called-off day is recorded as a bond event.

When does this guide not solve the problem?

This guide does not diagnose a reproducible platform defect from a screenshot alone. If a single-device report remains wrong, a saved limit changes without another synced device, or enforcement repeatedly misses a controlled test after restart and updates, the next step is evidence and support — not a confident theory about background processes or a particular iOS release.

That caution applies to the public reports quoted above as well. People post about Screen Time when it disappoints them, and the reports cluster after iOS releases — which is what you would expect both from a genuine regression and from ordinary attention, since an update is when people notice a setting again. Several posters attributed their problem to a specific iOS version. We have not verified any of those attributions, and neither should you before checking your own configuration: the same symptom is produced far more often by a category selection, a Customize Days entry, or Always Allowed than by a platform bug.

Use those threads for what they are good for — knowing which check to run next — and not as a diagnosis.

It also does not replace parental-control, school-device, workplace, or safety policies. For a child’s device, the family organiser manages the passcode from their own device. For a managed device, contact the administrator rather than trying to remove restrictions.

Frequently asked questions

Why can I still open an app after its Screen Time limit?

Check whether the app is in Always Allowed, whether App & Website Activity is on, and whether the correct app or category is in the limit. If the device owner knows the Screen Time passcode, they can also change or remove the limit.

Can Apple Screen Time report the wrong number?

A surprising total is not automatically a counting error. When Share Across Devices is on, reports and usage can include an iPhone, iPad, and Mac on the same Apple Account; select one device in the Screen Time report before escalating a suspected error.

How do I reset a forgotten Screen Time passcode?

Apple’s official recovery route is Settings › Screen Time › Change Screen Time Passcode › Change Screen Time Passcode, then authenticate with the Apple Account used for Screen Time Passcode Recovery. A family organiser resets a child’s passcode from the organiser’s own device; follow Apple’s current passcode-recovery instructions rather than third-party removal software.

Does deleting and reinstalling an app reset its Screen Time limit?

Do not rely on reinstalling. Apple’s documented way to remove a built-in App Limit is to delete that limit under Settings › Screen Time › App Limits; a third-party blocker may also lose its own local selection or permission when reinstalled.

Start with the configuration, narrow the report to one device, and change one layer at a time. If the controlled test still fails, preserve the evidence and take it to the system or app owner who can investigate it.