A university student in the United States has been locked out of his iPhone after Apple removed a diacritical character — a háček — from its Czech keyboard layout in a recent software update, rendering his alphanumeric passcode impossible to enter on the lock screen.
A university student in the US has found himself in what he describes as 'data limbo' following an Apple software update that quietly removed a key character from the iPhone's Czech keyboard, blocking access to his device.
The student had set an alphanumeric passcode containing a háček — a diacritic mark commonly used in Czech and other Central European languages, appearing above letters such as č, š, and ž. Following the update, Apple's lock-screen keyboard no longer displays or accepts that character, making it impossible for him to authenticate and gain entry to his phone.
The incident highlights an often-overlooked risk in software updates: changes to input methods or keyboard layouts can have cascading, unintended consequences for users who have incorporated non-standard characters into their security credentials. While Apple frequently updates its keyboard software to improve language support, autocorrect, and regional character sets, such changes are rarely flagged in release notes with enough specificity for individual users to anticipate problems.
The affected student has not yet been able to recover access to his device, and it remains unclear whether Apple's standard account recovery processes can help in cases where the passcode itself cannot be physically typed. Apple's data recovery options are deliberately limited by design — a security feature intended to protect users from unauthorised access — but that same design can work against legitimate owners in edge-case scenarios like this one.
Apple had not publicly commented on the specific case at the time of publication. The company's support documentation advises users who are locked out of their devices to use recovery mode, which involves erasing the device entirely — a process that would result in data loss if the student does not have a recent backup.
The story drew significant attention in technology communities, with many users noting that it serves as a cautionary tale about the use of special or non-ASCII characters in device passcodes. Security experts have long recommended longer, complex passcodes, but this case illustrates that complexity can introduce unexpected vulnerabilities when software environments change beneath users' feet.
It is not known how many other users may be affected by the same keyboard change, or whether Apple is aware of the issue and working on a fix.
Analysis
Why This Matters
- Users who rely on non-English characters in passcodes or passwords face an invisible risk: software updates can silently remove their ability to authenticate, effectively locking them out of their own devices.
- Apple's strong encryption and anti-recovery design, while beneficial for security, can cause permanent data loss in edge cases like this — raising questions about whether users need better warnings when keyboard changes could affect passcode entry.
- The case may prompt broader discussion about how Apple and other platform vendors communicate low-level keyboard changes that could affect security credentials.
Background
Apple has long promoted the use of alphanumeric passcodes as a more secure alternative to simple numeric PINs, and iOS supports multiple keyboard languages on the lock screen. However, the lock-screen keyboard environment is a stripped-down version of the full iOS keyboard, and its support for regional or diacritical characters has historically been inconsistent.
Diacritic marks — such as the háček used in Czech, Slovak, Croatian, and other languages — are standard characters in those writing systems but are sometimes treated as edge cases in software internationalisation. Keyboard layout changes are typically bundled into broader iOS point releases, and Apple does not routinely alert users when specific characters are added or removed.
Apple's approach to device security is deliberately designed so that even Apple itself cannot unlock a device on behalf of a user. This 'secure enclave' architecture has been central to several high-profile legal disputes, including the 2016 FBI case involving an iPhone linked to the San Bernardino attack. While widely praised by privacy advocates, it means that lock-out scenarios carry significant consequences.
Key Perspectives
Affected Users: Anyone using a non-ASCII character in a passcode faces the same theoretical risk. The student's situation is an extreme example of a problem that could affect a broader population of multilingual iPhone users.
Apple: The company has not commented publicly on this specific case. Apple's general position is that its security architecture protects user data, and that recovery mode — which erases the device — is the intended path for locked-out users.
Critics/Skeptics: Security and usability researchers argue this case exposes a gap in Apple's update communications. A keyboard change that affects passcode entry should, at minimum, trigger a warning prompting users to verify they can still access their device before the update completes.
What to Watch
- Whether Apple acknowledges the keyboard change and issues a patch restoring the háček to the lock-screen Czech keyboard layout.
- Whether the affected student can recover his data through backup services such as iCloud, or faces permanent loss.
- If other users come forward with similar lock-out experiences following the same update, which would indicate the problem is broader than a single isolated case.