If you have an Apple device running iOS 18 or iOS 26 and gone looking for the old Get Verification Code option under Settings → [user name] → Sign-In & Security, you’ve probably noticed it’s no longer there. A quick search turns up forum threads, support comments, and even GitHub issues all reaching the same conclusion: Apple removed it. Some posts go further and call it “deprecated” or “Apple’s middle finger to users of older devices.” That conclusion is wrong. The option still exists in iOS 26. It just doesn’t show up the way it used to.
Offline verification codes are still available in iOS 18 and 26. The catch is that the Get Verification Code button now appears only when your iPhone itself is offline – Airplane Mode on, or no network connection. When the device is online, iOS no longer shows the option in Sign-In & Security at all, which is why people assume it’s gone.
That’s the whole source of the confusion: users check on a connected phone, see nothing, and conclude the feature was killed.
Here’s how to request a 6-digit two-factor authentication code:
The “Account Details Unavailable” pop-up is expected behavior, not an error. It’s simply the surface Apple chose for the offline path – the device can’t load live account details with no connection, so it offers the offline code generator instead.
This is a behavior change, not a removal. When your iPhone is connected, iOS pushes the sign-in code to your trusted devices automatically, so Apple dropped the manual entry from Sign-In & Security on connected devices in iOS 26. Earlier versions of iOS keep the manual Get Verification Code option in Settings even while the device is online – which is why an old iPhone on iOS 15, 16, or 17 still shows it where you expect, and why those screenshots float around forums “proving” the feature still exists. It does exist; it’s just gated behind the offline state now on current iOS.
So the practical state of play across versions:
The offline code path is the fallback that keeps people from getting locked out – signing in to iCloud.com, onto a second device, or onto older hardware that can’t receive a pushed code on its own. The reports that it was “removed” are misleading, and acting on them (for example, telling someone their only option is an old device on iOS 17) sends people down the wrong path. The feature is there in iOS 18 or iOS 26. You just have to take the phone offline to see it.
For forensic examiners, the stakes are more concrete. Cloud extraction from iCloud with tools such as Elcomsoft Phone Breaker requires passing two-factor authentication on the target account. The usual “push code to a trusted device” route is generally a non-starter here: the evidentiary device can’t be brought online, so no pushed code will ever arrive. That leaves the offline path as the practical way through. As long as the examiner can reach Sign-In & Security on a trusted device that’s been taken offline, generating the six-digit code by hand keeps the extraction workflow moving. The iOS 26 change doesn’t close that door – it just hides the handle until the device is offline, which, in this scenario, it already is.