App Limits not working on iOS 26: the fix for each symptom
Most "App Limits not working" cases on iOS 26 are not bugs. They are the default behaviour of a feature Apple designed to be ignored. This page matches each symptom to the switch that causes it, quoting Apple's own iOS 26 guide, and then covers the one iOS 26 problem developers have actually reported, which affects usage-based blockers and not scheduled ones.
The short answer
- Apple's iOS 26 guide says limits "can be ignored once reached" by default. An app opening after its limit is the design, not a failure.
- The switch that stops the ignoring on iPhone is Block at Downtime, and Apple's guide only offers it once a Screen Time passcode is set. No passcode, no hard block.
- One tap on Turn Off App & Website Activity removes every limit, and one swipe deletes a limit. If limits keep vanishing, that is the door.
- The only real iOS 26 defect we could find is in the developer framework: usage thresholds firing immediately (reported for iOS 26.5.2, no Apple reply). Scheduled blocks run on a different path.
Everything quoted below is from Apple's iPhone User Guide for iOS 26 or Apple's developer documentation, opened on 2026-09-12. Where we could not find a statement on an Apple page, the text says so.
Symptom by symptom: what Apple's guide says is happening
Work down the table. The first column is what you see; the third is the sentence on Apple's page that explains it.
| What you see | Cause | Apple's wording (iOS 26 guide) | Fix |
|---|---|---|---|
| The limit screen appears, then the app opens anyway | Default behaviour | "By default, Screen Time limits can be ignored once reached." | Move the app into Downtime and turn on Block at Downtime (steps below) |
| Downtime shows a reminder but the app still works | Block at Downtime is off | "When Block at Downtime is off, you see a reminder that it's downtime, but you can choose to continue using the apps." | Settings › Screen Time › Downtime › Block at Downtime |
| Block at Downtime is not in the menu | No Screen Time passcode | "If you set a Screen Time passcode for yourself or your child, you can choose whether apps are completely blocked or just dimmed during downtime." | Set a passcode first (Lock Screen Time Settings), then return to Downtime |
| All limits disappeared at once | App & Website Activity was turned off | "Turning off App and Website Activity turns off reporting, Downtime, App Limits, and Always Allowed." | Turn App & Website Activity back on; put a passcode in front of it |
| One limit is gone | It was deleted | "Tap App Limits, swipe left on a limit, then tap Delete." | Recreate it; the passcode is the only thing that makes the swipe cost anything |
| The limit never triggers on one app | The app is in Always Allowed | Always Allowed apps "stay available during downtime and after you reach time limits." | Settings › Screen Time › Always Allowed, remove the app |
| The limit runs out faster than you used the app on this phone | Share Across Devices is on | "When Share Across Devices is on, any Screen Time limits or schedules you set apply to your iPhone, iPad, and Mac." | Expected: use on iPad counts. Turn it off only if you want separate budgets per device |
| The limit is different on some days | Customize Days | "To set an amount of time for each day, tap Customize Days, then set limits for specific days." | Open the limit and check each weekday |
Two things are worth reading twice. First, Apple's page does not describe a block-at-end-of-limit switch for App Limits on iPhone at all. It describes one for Downtime. The macOS guide does document a "Block at end of limit" checkbox for Mac limits, so if you see a similar switch inside an iPhone limit, turn it on, but we could not find it in the iOS 26 guide and treat its presence as unverified. Second, the Block at Downtime paragraph is conditional on a passcode. People who "set up Downtime and it does nothing" have usually skipped the passcode, so the switch never appeared.
The fix in order (10 minutes, once)
This is the sequence that turns the nudge into a wall using nothing but Apple's settings. Do it in the afternoon, not at midnight.
- Settings › Screen Time › App & Website Activity › make sure it is on. Apple's guide calls this the easiest way to turn Screen Time off, so it is also the first thing to check.
- Settings › Screen Time › Lock Screen Time Settings › someone you trust enters a four-digit passcode twice while you look away. Apple: once set, it "must be entered before you can change the settings you've chosen for yourself."
- Settings › Screen Time › Downtime › Scheduled › Every Day or Customize Days, then the hours you already know you lose.
- Same screen › Block at Downtime › on. Apple: "restricted apps can't be opened during downtime—they appear dimmed with an hourglass icon."
- Settings › Screen Time › Always Allowed › remove anything that should not survive downtime. Apple's default list is the place limits quietly fail.
- Keep App Limits for apps you still want to ration during the day, knowing the limit screen will let you through. That is fine for a budget; it is not fine for a wall.
If the thing you keep doing is tapping past the limit screen itself, the passcode-holder pattern is covered step by step in How to stop yourself from tapping Ignore Limit on Screen Time. The difference between the two tools is laid out in Downtime vs App Limits on iPhone.
The one iOS 26 problem developers actually reported
Third-party blockers use the same Screen Time system as Apple's settings, through the Family Controls, Device Activity and Managed Settings frameworks. There are two ways an app can ask that system to block something:
| Mechanism | What the app hands the system | Apple's description | iOS 26 reports |
|---|---|---|---|
| Usage threshold (a budget, like App Limits) | An event with a threshold, e.g. 30 minutes of use | Device Activity lets an app "warn the person once they have reached their threshold." | Two forum threads (July and August 2026) report the threshold callback firing immediately on iOS 26.5.2 and 26.x, before any real use, after which no shield is applied. No Apple reply. Unverified by Apple. |
| Calendar schedule (a window, like Downtime) | A start time, an end time, and whether it repeats | "A calendar-based schedule for when to monitor a device's activity." The system calls the app's extension when the interval starts and ends. | Not described as affected in those threads. The August poster asks whether a "DeviceActivitySchedule-based (wall-clock) approach" is the reliable path. |
We are quoting the reports, not confirming them. Apple has not replied in either thread as of the check date, and we have not reproduced the threshold bug ourselves. What we can say from our own device log is how the schedule path behaves: on an iPhone 14 running iOS 26.5, on 2026-08-09, a 15-minute scheduled interval was accepted, the shield was applied, and after a 15-minute break with the blocker app closed the shield came back on its own, one second late. Schedules of 5 and 10 minutes were rejected by the system with the documented intervalTooShort error, which Apple describes as "The activity's schedule has an interval that is too short." The floor is 15 minutes; that is the same unit Apple's own limit screen uses for its snooze.
The practical reading: a blocker that works from a daily time budget is exposed to the same two failure modes as Apple's App Limits (the budget can be ignored by design, and on iOS 26 the counting itself is reported to be unreliable). A blocker that works from a schedule is exposed to neither, because the system, not the app, starts and ends the interval, and a schedule has no budget to miscount. If your third-party limits stopped behaving on iOS 26, check which kind you are running before you blame the app.
Things people are told to try that Apple's pages do not mention
Restarting the phone, toggling Screen Time off and on, signing out of iCloud, resetting all settings. None of these appear on the Apple pages we opened for this article, so we list them as unverified rather than as fixes. They are harmless, but if they "work", it is usually because the toggle recreated a limit that had been deleted, or turned App & Website Activity back on. Check the table above first; it costs nothing.
One more report worth knowing about, again unverified by Apple: a developer thread from September 2026 quotes the Screen Time consent sheet as saying that Apple's Screen Time "will lose access to this data as only one app or service can access it at a time" when a third-party app is granted usage-data access. That concerns usage reports, not blocking, but if your Screen Time summary went blank after installing a blocker, that thread is the likely explanation.
Frequently asked questions
Why does my app still open after the App Limit is reached on iOS 26?
Because that is the default. Apple's iOS 26 guide says Screen Time limits can be ignored once reached. The limit screen offers a way to keep using the app. To remove that option on iPhone, Apple points you to Block at Downtime, which requires a Screen Time passcode to be set. For a limit that cannot be tapped past, put the app in Downtime with Block at Downtime on, and have someone else enter the passcode.
Do I need a Screen Time passcode for App Limits to work?
Not to count time, but yes to make a block hold. Apple's guide states that Block at Downtime is available if you set a Screen Time passcode for yourself or your child. Without a passcode, deleting a limit is one swipe and turning off App and Website Activity is one tap, and both remove every limit.
Is there an iOS 26 bug that breaks third-party app limits?
Developers have reported one on the Apple Developer Forums: usage-based thresholds in the Device Activity framework firing immediately on iOS 26.5.2, before any real use, so no shield is applied later. Apple has not replied in those threads, so treat it as unverified. Schedule-based blocks use a different mechanism, a calendar interval that the system starts and ends, and the reports do not describe that path as affected.
Unbudge: a schedule-based blocker for iPhone
Unbudge is built on the schedule path described above, not on usage budgets. You pick apps, set a window, and the system holds the block; a break is 15 minutes and the block returns on its own even if Unbudge is never reopened. It reads the shield state back and tells you when the block is not up, instead of staying silent. Free for 3 apps and 1 schedule.
Unbudge
ADHD app blocker for iPhone. Schedules, 15-minute breaks that relock on their own, no free trial that turns into a charge
Free for 3 apps and 1 schedule · Pro $29.99/year or $3.99/month, no free trial that converts · No account, data stays on the phone · How Unbudge works
Related guides
- Downtime vs App Limits on iPhone — the full comparison table and which tool fits which problem.
- Screen Time app limit resets at midnight — why limits are daily budgets and what to use when you need windows.
- How to stop yourself from tapping Ignore Limit on Screen Time — the passcode-holder pattern and the 15-minute floor.
- Deleting the app bypasses your blocker. Here is the fix — the Deleting Apps restriction, row by row.
- App blocker for ADHD: what actually works on iPhone — judge a blocker by its exits.
Sources
All checked on 2026-09-12.
- Apple, iPhone User Guide (iOS 26), "Set schedules with Screen Time on iPhone" — limits can be ignored by default; Block at Downtime; 5-minute reminder; Customize Days
- Apple, iPhone User Guide (iOS 26), "Get started with Screen Time on iPhone" — App & Website Activity; Share Across Devices; deleting a limit
- Apple, iPhone User Guide (iOS 26), "Create, manage, and keep track of a Screen Time passcode on iPhone"
- Apple, macOS User Guide, "Set time limits for apps and websites in Screen Time on Mac" — "Block at end of limit"
- Apple Developer Documentation, "Device Activity"
- Apple Developer Documentation, "DeviceActivitySchedule"
- Apple Developer Documentation, "DeviceActivityCenter.MonitoringError" — intervalTooShort
- Apple Developer Documentation, "Family Controls"
- Apple Developer Forums, thread 838510, "DeviceActivity eventDidReachThreshold fires immediately on iOS 26.5.2" (July 2026, no Apple reply)
- Apple Developer Forums, thread 840907, "Is local-time validation and re-arming a supported workaround for premature DeviceActivity thresholds on iOS 26?" (August 2026, no Apple reply)
- Apple Developer Forums, thread 844661, "Is there a way to coexist with Apple's Screen Time?" (September 2026, no Apple reply)
- KANAU WORKS device log, iPhone 14 on iOS 26.5, 2026-08-09: schedules of 5 and 10 minutes rejected with intervalTooShort, 15 and 20 minutes accepted; shield returned 1 second late after a 15-minute break with the app closed.