Apple Working on Fix for iOS 26 iPhone Lockout Bug

Apple is developing a software fix for a critical bug in iOS 26 that has permanently locked some iPhone users out of their devices after updating to the latest operating system. The issue stems from the removal of the caron character (č) from the Czech keyboard layout in iOS 26, which was released in September 2025. Users who had set custom alphanumeric passcodes containing this character found themselves unable to unlock their devices following the update, as the character was no longer available on the lock screen keyboard.

The bug affects users who rely on non-English keyboard layouts for their passcodes, particularly those using Czech or other Central European language inputs that include diacritical marks. When Apple removed the caron character from the iOS Czech keyboard in iOS 26, it inadvertently broke access for anyone who had incorporated that character into their alphanumeric passcode. Since iOS does not allow passcode changes without first unlocking the device, affected users face a full factory restore as the only recovery option — a process that erases all data unless a recent backup exists.

One affected user, identified as Byrne in reporting by gHacks, described the situation as both frustrating and avoidable. Byrne had set a custom alphanumeric passcode that included the caron character, which was accessible on the Czech keyboard in earlier versions of iOS. After updating to iOS 26, the character disappeared from the keyboard, making it impossible to enter the passcode. Byrne noted that the removal resulted in two identical characters appearing side by side on the lock screen keyboard, a visual anomaly that should have been caught during quality review.

Despite the inconvenience, Byrne acknowledged Apple’s rapid response to the issue. “On one hand, it’s impressive that they’re working on a fix within nine days of the issue being reported,” Byrne told gHacks. “On the other, it’s hard to believe that the breaking change was ever approved.” He added that he plans to switch to Android regardless of whether the fix is released, citing superior camera quality as his primary motivation for the platform change.

Apple has not yet issued an official statement regarding the bug or provided a timeline for when the fix will be included in a public iOS 26 update. The company has not responded to press inquiries about the matter, and the fix has not been assigned to a specific upcoming release. As of now, there is no public beta or developer seed containing the patch, leaving affected users without an immediate workaround short of data-loss recovery.

Users who have not yet updated to iOS 26 are advised to verify that their current passcodes can still be entered using the available keyboard layouts before installing the update. Those who rely on special characters from non-English keyboards should consider temporarily switching to a basic numeric or alphanumeric passcode using only universally available characters to avoid potential lockout. Apple typically recommends using passcodes composed of characters present across all supported keyboard layouts to prevent such issues.

This incident highlights ongoing challenges in balancing keyboard localization changes with system-level security features like passcode entry. While iOS supports a wide range of languages and input methods, modifications to keyboard layouts must account for their unintended consequences on user authentication systems. The bug underscores the importance of regression testing across accessibility and internationalization features, particularly when changes affect low-level input handling.

For now, affected users remain in limbo, awaiting a software update that restores access to their devices without requiring data loss. Until such a fix is released, the incident serves as a cautionary example of how seemingly minor localization adjustments can have significant downstream effects on user experience and device accessibility.