ARTICLE AD BOX
After updating to iOS 26, I’m experiencing an issue where some characters are not recognized when typing quickly on the keyboard.
The problem happens only in my app. Other apps on the same device do not show this behavior. Maybe they are using UIKit idk.
What makes this confusing is that the issue still occurs even in a fully isolated setup:
- A single SwiftUI view
- Only a TextField bound to a @State String
- No onChange, no timers, no animations, no extra layout work
struct MyView: View { @State var inputText = "" var body: some View { TextField("placeholder", text: $inputText) // UIKitTextField(text: $inputText, placeholder: "placeholder") } } struct UIKitTextField: UIViewRepresentable { @Binding var text: String var placeholder = "" func makeUIView(context: Context) -> UITextField { let tfx = UITextField() tfx.placeholder = placeholder tfx.delegate = context.coordinator tfx.addTarget(context.coordinator, action: #selector(Coordinator.changed), for: .editingChanged) return tfx } func updateUIView(_ uiView: UITextField, context _: Context) { if uiView.text != text { uiView.text = text } } func makeCoordinator() -> Coordinator { Coordinator(text: $text) } final class Coordinator: NSObject, UITextFieldDelegate { @Binding var text: String init(text: Binding<String>) { _text = text } @objc func changed(_ sender: UITextField) { text = sender.text ?? "" } } }I also tried replacing SwiftUI TextField with a UIKit UITextField using UIViewRepresentable, but the result is the same.
Symptoms:
- Some keystrokes are completely dropped (the character never appears in the bound String)
- Keyboard key popover animations sometimes do not play when typing fast
Additional details:
- The view is presented inside a UIHostingController
- Autocorrection / predictive text on or off does not change the behavior
- Keyboard layout is Turkish QWERTY
Has anyone encountered a similar issue on iOS 26?
Could this be related to SwiftUI + UIHostingController, or a known keyboard/input regression in iOS 26?
Any insights or confirmed workarounds would be greatly appreciated.
