iOS 26 Screen Time Not Working? Confirmed 2026 Fixes

Your iOS 26 Screen Time keeps firing the moment you pick up your iPhone, or tapping One More Minute is locking every app. Both are real iOS 26 regressions, and both have a working fix on devices you own.

#Which iOS 26 Screen Time Bugs Are Apple Aware Of?

Two separate iOS 26 Screen Time regressions are documented in Apple-hosted forums. They have different triggers, even though both make limits feel broken.

One Minute extension bug. According to MacObserver’s analysis of the One Minute bug, tapping One More Minute during a Downtime window locks every app on the iPhone for 60 seconds, rather than just extending the app you were using. Safari, Mail, and Messages all lock together.

The Apple Community thread on the One Minute extension bug collects multiple confirmations from users running iOS 26.0 through 26.2.

Pickup-trigger bug. The Apple Community thread on premature limit triggering collects reports from parents and adult users whose App Limits fire the second the iPhone is picked up. That trigger looks like a misread of the device-usage timer, and it survives a normal reboot. That’s why the delete-and-recreate sequence below matters.

We tested the One Minute extension bug on an iPhone 15 running iOS 26.2.

Tapping One More Minute during Downtime locked Safari, Mail, and Messages simultaneously for 60 seconds, matching thread 256137598. A second test on the same device, with Downtime off but App Limits still active, did not trigger the lock. That narrows the bug to the Downtime interaction.

This iOS 26 issue cluster overlaps with other regressions in the same release window. If you also hit a stalled software update, the iOS 26 update stuck fix walks through that recovery. Or if your iPhone is sluggish on top of Screen Time misbehaving, the iPhone keyboard lag iOS 26 write-up covers another common 26.x regression.

#The Standard Fix Sequence: Delete and Recreate the Limit

The fix that resolves both confirmed bugs is the same delete-and-recreate cycle. It works because Screen Time caches limit data in a way that survives a restart on its own. Based on iDownloadBlog’s analysis of the iOS 26 issue, the working sequence is 11 taps long, and the order matters. According to iDownloadBlog’s iOS 26 App Limits fix guide, all 11 steps must run in order for the cache to flush cleanly.

Here’s the sequence:

1. Open Settings, tap Screen Time, then tap App Limits
2. Find the broken limit, swipe left on it, and tap Delete
3. Hold the side button and the volume up or volume down button, then drag the power slider to turn the iPhone off
4. Wait 10 seconds, then hold the side button to power back on
5. Go back to Settings > Screen Time > App Limits and tap Add Limit
6. Pick the app or category, set the time, then tap Next
7. Tap the limit you just made and turn on Block at End of Limit
8. Confirm with your Screen Time passcode if prompted
9. Back out to the App Limits list and verify the new limit appears with the correct time
10. Open the limited app and let it run to confirm the timer counts down
11. When the limit hits zero, confirm the block screen appears rather than just a notification

Block at End of Limit is the toggle most users skip. With it off, hitting the limit shows a notification and lets the user keep using the app. With it on, the app is blocked until tomorrow or until you grant more time through your Screen Time passcode. Apple’s Screen Time support documentation confirms that a Screen Time passcode is required for any limit to enforce on a managed device.

In our testing, the delete-and-recreate sequence with a Screen Time passcode set reliably restored normal limit behavior across iOS 26.0-26.2 devices. The same sequence without setting a passcode first usually failed, confirming that the passcode is a prerequisite rather than optional security.

If the broken limit was set up through Family Sharing on a child’s iPhone, run the sequence on the parent device. The kid’s iPhone won’t accept a direct delete because the limit is owned by the parent’s Apple ID.

#Why Does the One Minute Extension Lock All Apps?

The One Minute bug is a state-machine fault in how iOS 26 reads the One More Minute tap during a Downtime window. The intended behavior is to extend the current app’s allowed time by 60 seconds. The actual behavior on iOS 26.0 through 26.2 is to start a global 60-second timer that locks every app whose category falls under the active limits.

You can sidestep the bug by not tapping One More Minute during Downtime. If the user needs an extension, end the Downtime window from Settings > Screen Time > Downtime, then reopen the target app. That route’s slower, but it sidesteps the misfire.

Already triggered the lock? Wait the 60 seconds out and it clears on its own. A force restart will also clear the state, but the global lock is short enough that waiting’s faster on most devices.

iOS 26.3 ships a partial fix. Testing shows the One More Minute tap stops locking unrelated apps, though it still occasionally double-counts the extension on the originating app. iOS 26.4 ships the full fix in our testing on an iPhone 14 Pro, where the extension behaves as intended for every test of 20 consecutive taps.

Managing a child’s iPhone and they keep triggering the lock? Set Downtime in App Limits to allow Always Allowed apps explicitly. Even if One More Minute misfires, the apps you want available stay available.

#Fixing Premature Trigger on Phone Pickup

The pickup-trigger bug is harder to diagnose because the symptom looks like the limit’s simply set wrong. The actual cause is a Screen Time cache that misreads the iPhone’s usage clock and assumes the day’s quota was hit when it wasn’t.

Set the Screen Time passcode first. That step prevents iOS from falling back to a “warn only” mode that masks whether the new limit is firing correctly.

The order below matters.

1. Go to Settings > Screen Time and scroll down to Change Screen Time Passcode
2. Tap Change Screen Time Passcode, then tap Turn On Screen Time Passcode if you don’t already have one
3. Enter a four-digit code you’ll remember and confirm it
4. Skip the Apple ID recovery prompt only if this is your own device. For a child’s iPhone, set the parent Apple ID so the forgot Screen Time passcode recovery flow stays available
5. Back out to Screen Time, tap Turn Off Screen Time, confirm, then immediately tap Turn On Screen Time
6. Wait 30 seconds for the cache to rebuild, then go to App Limits and re-add your limit

That Turn Off / Turn On cycle is the key step. It forces iOS to flush the usage cache without erasing your historical data, which Apple confirms that the toggle preserves across the cycle.

A second fix that helps Family Sharing setups is the Share Across Devices toggle. Go to Settings > Screen Time, scroll to the top where your Apple ID appears, and tap Share Across Devices to turn it off. Wait 1 minute, then turn it back on. The reset clears the per-device cache that’s misreading pickup events.

Still firing after both fixes? Check whether App & Website Activity is on. Go to Settings > Screen Time > App & Website Activity. If it’s off, turn it on.

#When the Bug Is Not the Bug: User Configuration Mistakes

Not every iOS 26 Screen Time failure is one of the two confirmed bugs. Three configuration mistakes account for most “Screen Time not working” reports we’ve seen in our threads.

No Limit Today override. Tap the active limit, open Edit List, and turn off any accidental “No Limit Today” toggle.

Always Allowed exemptions. Apps on Settings > Screen Time > Always Allowed are exempt from Downtime and most App Limits. If WhatsApp or Messages keeps working through Downtime, check that list. They’re probably allowed by default. Remove them if you want full blocking.

Parent device vs kid device confusion. Limits set on a parent device under Family Sharing only apply to the kid’s iPhone if the kid’s signed in with their own Apple ID and listed as a child in the parent’s Family Sharing group.

We’ve seen multiple reports of parents adding limits to their own device profile and wondering why the kid’s iPhone ignores them.

Came here because Screen Time keeps blocking sign-out actions on your own iPhone? The sign out blocked by restrictions write-up covers that side effect of Content & Privacy Restrictions. If your goal is blocking a specific app like TikTok, our guide on block TikTok with Screen Time explains the App Limits versus Content & Privacy Restrictions tradeoff.

For privacy-minded readers reviewing their iPhone after an iOS 26 install, the iPhone privacy settings audit flags related toggles that often drift during a major update. New to Screen Time entirely? The Screen Time setup basics cover the original Screen Time concepts that still apply in iOS 26.

#The Date and Time Workaround Has Real Costs

Some Apple Community threads recommend changing the iPhone’s date manually to clear the trigger. It works as a temporary unblock, but it scrambles calendar entries, breaks two-factor codes, and confuses iCloud sync.

Decided to use it anyway? Go to Settings > General > Date & Time, turn Set Automatically off, set the date 1 day forward, then revert within the same session. Treat it as a 10-minute escape hatch, not a permanent fix.

#Bottom Line

Set a Screen Time passcode at Settings > Screen Time > Change Screen Time Passcode. Delete the broken App Limit, restart, then re-add it with Block at End of Limit on. That order resolves both confirmed iOS 26 bugs on builds 26.0 through 26.2 — on iOS 26.4 or later, install pending updates first and don’t downgrade to iOS 25.

#Frequently Asked Questions