An iPhone that refuses to finish a passcode change until an hour has passed is not frozen, not corrupted, and not rejecting the passcode being typed. The action is on a list Apple publishes, and the wait is the documented behavior of a feature called Stolen Device Protection. The fastest legitimate way out is not a restart, a reset, or a support call. It is to bring the iPhone to a place it already treats as familiar, because Apple states that the delay can end early there.
The second thing worth knowing is that the hour is not universal. Apple splits the affected actions into two groups of different sizes, and only one of them involves waiting at all. Away from familiar locations, ten actions demand a face or fingerprint and nothing else. Eight actions demand a face or fingerprint, then an hour, then a face or fingerprint again. Knowing which group an action belongs to answers the question faster than any troubleshooting step.
The Fastest Route Out of the Hour
- Move the iPhone to a familiar location. Apple's support page states it directly: "Your iPhone may end the security delay early after it detects that you've arrived at a familiar location." A home or a workplace is the example Apple gives. This is the only shortcut any of Apple's pages describes.
- If returning is not possible, complete the first authentication now. Apple describes the order without ambiguity: authenticate with Face ID or Touch ID, wait for the security delay to end, then authenticate with Face ID or Touch ID again. Leaving the screen before the first check is done means the sequence has not been entered.
- Authenticate a second time once the hour is up. The Personal Safety User Guide puts it as a single requirement: "Some security actions such as changing your Apple Account password also require you to wait an hour and then perform an additional Face ID or Touch ID authentication."
- Check whether the action even has a delay. Ten of the restricted actions have no waiting period at all. They fail for a different reason, covered below, and waiting an hour will not change their outcome.
- Confirm the five prerequisites are still switched on. Stolen Device Protection cannot be active without all five, and the settings path is
Settings > Face ID & Passcode > Stolen Device Protection.
The feature arrived with iOS 17.3, according to Apple's page, which carries a published date of July 31, 2026 in its current revision. Anything earlier than iOS 17.3 will not show the setting, which is itself a useful diagnostic: a device that has never offered the option is not the device producing this symptom.
Two Lists Decide Whether an Hour Is Involved
The ten actions that never wait
Away from a familiar location these require Face ID or Touch ID, and Apple's page is specific that the passcode is not an accepted substitute. Typing the passcode repeatedly is the single most common wasted effort in this whole symptom. The list Apple publishes covers: using passwords or passkeys saved in Keychain; using payment methods saved in Safari through AutoFill; turning off Lost Mode; opening a locked app; erasing all content and settings; applying for a new Apple Card; viewing an Apple Card or Apple Cash virtual card number; certain Apple Cash and Savings actions in Wallet; using the iPhone to set up a new device through Quick Start; and setting up or transferring an eSIM.
Two of those deserve a flag because they are the ones people hit at the worst possible moment. Quick Start and eSIM transfer both sit on this list, which means a phone with a cracked or non-responsive Face ID sensor can block a migration to a new handset even though the owner knows every password involved. That is a hardware problem wearing a software mask, and no amount of waiting resolves it.
The eight actions that wait an hour
These are the ones that produce the symptom in the title: changing the Apple Account password; signing out of the Apple Account; updating Apple Account security settings such as trusted devices, a Recovery Key, or a Recovery Contact; adding or removing a Face ID or Touch ID enrollment; changing the device passcode; Reset All Settings; enrolling in Mobile Device Management; and turning off Stolen Device Protection itself.
The pattern across those eight is consistent. Every one of them would, if completed by a thief, hand over lasting control of the account or lock the rightful owner out. The ten on the first list are immediate-value actions. The eight on the second list are permanent-change actions. That distinction, not any hidden setting, is what decides whether an hour is involved.
What the Hour Looks Like in Apple's Sequence
Two authentications, not one. That detail explains a complaint that otherwise sounds like a bug: someone waits the full hour, returns to the screen, and the change still does not go through. Nothing failed. The second Face ID or Touch ID check had not been performed yet. Apple's wording places it after the wait, as an additional authentication rather than a repeat of the first.
What none of Apple's four pages state is what happens to the hour if the iPhone is restarted, powered down, or taken off the network in the middle of it. That silence is worth respecting rather than filling in. Treat a restart as an unknown, not as a reset and not as a preserved timer, and plan around the familiar-location behavior instead, which is the one path Apple does describe.
The Five Requirements, and Where They Live
The five prerequisites are the first thing to audit when the feature behaves unexpectedly, because Apple lists all of them as conditions rather than suggestions: two-factor authentication on the Apple Account, a device passcode, Face ID or Touch ID, Find My turned on, and Significant Locations under Location Services. Apple's page also notes that Find My cannot be switched off while the feature is active, which is a deliberate one-way door and not a stuck toggle. A Find My message about a device being removed on an unchosen date is an entirely separate situation, and the reasoning behind that one is set out in a walkthrough of Find My removal dates.
Two-factor authentication being a hard requirement also means the trusted-device and trusted-number layer sits underneath everything here. When codes themselves start failing, the cause is usually unrelated to theft protection and closer to a clock problem, which is covered in the breakdown of authenticator codes rejected after clock drift.
Why a Theft Feature Reads Location At All
The familiar-location behavior is the part that generates the most suspicion, so it is worth stating what Apple publishes about the underlying data. Significant Locations is one of the five prerequisites, and it appears at Settings > Privacy & Security > Location Services > System Services > Significant Locations & Routes on an iPhone. The same Personal Safety guide that gives that path adds a one-line statement about the data: "Significant locations are encrypted and can't be read by Apple."
Apple's legal documentation on Location Services goes further on the sync question, stating that "Your Significant Locations & Routes are synced between your devices using end-to-end encryption and cannot be read by Apple." The same page describes what the feature collects in its own words: devices signed in to iCloud with an Apple Account "will keep track of places you have recently been, how often and when you visited them, and the routes you take to get there, in order to learn places and routes that are significant to you."
That is the whole documented picture. Anyone uncomfortable with it has a straightforward option: the same Location Services screen allows individual locations to be removed from the list, or all of them cleared at once. The trade-off is direct rather than hidden. Fewer familiar locations means fewer places where the hour can be cut short, and a cleared history means the default behavior has less to work with.
The Case That Looks Like a Fault: Selling or Trading In
A device being prepared for sale runs into both lists at once, and the result reads like a broken phone. Erasing all content and settings sits on the biometric list, so away from a familiar location it needs a working Face ID or Touch ID. Turning off Stolen Device Protection sits on the delay list, so away from a familiar location it starts an hour. Apple addresses the second point explicitly, noting that attempting to turn the feature off outside a familiar location starts a security delay first, and adding the instruction plainly: "You should turn off Stolen Device Protection before you sell, give away, or trade in your iPhone."
The practical order for anyone handing a device over is therefore fixed rather than optional. Do it at home or at work, not at the counter of a trade-in store. Turn the feature off first, confirm it is off, and only then erase. Reversing those two steps is what produces the trade-in counter scenario where a customer is told to come back in an hour.
Two Failure Modes That Are Not This
An Apple Account password that is rejected outright is a different symptom with a different cause path. A security delay never says the password is wrong. It says the change cannot complete yet. When the account itself refuses a password that is known to be correct, the exact wording on screen is what narrows it down, and that separation is worked through in the guide to Apple Account password rejections and error wording.
The other lookalike is a Face ID sensor that has stopped working. Because ten actions accept no passcode fallback, a failed sensor produces a wall with no visible timer attached. The tell is the absence of an hour: a security delay announces a wait, while a sensor fault simply refuses. If Face ID has also stopped unlocking the device normally, the problem is not Stolen Device Protection and the hour is a red herring.
When This Doesn't Apply
Devices below iOS 17.3. Apple states the feature is available with iOS 17.3 or later. An older iPhone that makes someone wait to change a passcode is doing so for some other reason, and none of the two lists above apply to it.
iPad, Mac, Apple Watch and Apple TV. Every page cited here is written for iPhone. Nothing in Apple's documentation extends Stolen Device Protection to other device classes, and assuming a parallel feature exists elsewhere is guesswork.
Managed or company-owned devices. Enrolling in Mobile Device Management appears on the delay list, which means an organization's enrollment step can itself be delayed. What a management profile can or cannot override once enrolled is not addressed on any of the pages cited here, so a corporate device that behaves differently should be raised with whoever administers it rather than diagnosed from consumer documentation.
The always-on choice. The default applies the additional measures only away from familiar locations. Apple also offers a choice that enforces them regardless of location. On a device set that way, standing in the kitchen changes nothing, and the familiar-location shortcut described above will not help.
A forgotten passcode. None of this covers a device whose passcode is genuinely unknown. That is an account recovery path, not a security delay, and it is governed by completely separate Apple procedures.
Anything about the hour that Apple has not published. The behavior of the timer across reboots, shutdowns, airplane mode, time-zone changes or a manually altered device clock is not stated on any of the four pages cited here. Those questions have answers, but the answers are not in the documentation, and inventing them is how people end up troubleshooting a feature that is working correctly.
What To Have Ready Before Contacting Apple
A support conversation goes faster with four specific facts in hand, and all four are checkable in under a minute. First, the exact action that triggered the wait, named as it appears on Apple's list rather than described loosely. Second, whether the device was at a location it would plausibly treat as familiar. Third, the iOS version, since anything below 17.3 rules the feature out entirely. Fourth, whether Face ID or Touch ID is working for ordinary unlocking, which separates a delay from a sensor fault immediately.
Worth stating clearly as a closing point: an hour-long wait on this list is not evidence of a compromised account, a failing device, or a software defect. It is the feature doing the one thing it was built to do, at the one moment it is most inconvenient, which is precisely the design. The only genuine fault worth chasing is the one where the hour passes, the second authentication is performed, and the change still does not complete. That case is not documented anywhere in Apple's published material, and it is the one that belongs in a support ticket.
Sources
- Apple Support, About Stolen Device Protection for iPhone - iOS 17.3 availability, both action lists, the one-hour delay, the familiar-location early end, and the sell or trade-in instruction.
- Apple Personal Safety User Guide, Use Stolen Device Protection on your iPhone - the Settings path and the default familiar-location wording.
- Apple Personal Safety User Guide, Manage Location Services settings - the Significant Locations and Routes path and the statement that the data is encrypted.
- Apple Legal, Location Services and Privacy - what Significant Locations and Routes records and the end-to-end encryption statement.
Comments
Post a Comment