You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Orca mobile Android, Korean Hangul input is decomposed into separate jamo characters. #6995
Also reproducing on iOS — iPhone 17 Pro. This is not Android-only; the title/labels (os:mobile-beta / Android) undersell the scope.
Environment
Device: iPhone 17 Pro
Keyboard: iOS system Korean (2-set / 두벌식)
Input surface: Orca mobile chat/agent input field (remote input)
Symptom — identical to the original report:
Expected: 안녕하세요
Actual: ㅇㅏㄴㄴㅕㅇㅎㅏㅅㅔㅇㅛ (decomposed jamo, no syllable composition)
So the IME composition/preedit handling issue affects both Android (Samsung Keyboard) and iOS system keyboard, which points to the mobile input field consuming intermediate/per-jamo change events instead of waiting for the composed (committed) text. Likely the same root cause as the terminal-side #7000, but in the chat input surface. +1 on P1.
I dug into this with a full local repro environment and can narrow the root cause significantly.
Setup
Android 14 emulator (arm64), Orca mobile dev build from current main
Paired against mobile/scripts/mock-server.ts (with a locally added session.tabs.list handler so the session screen finishes loading, and a logger on terminal.send to capture exactly what the app sends)
Gboard, Korean 2-set (두벌식) — typed 안녕하세요 key-by-key into the terminal live input field
Result: does NOT reproduce with Gboard
The captured terminal.send stream shows correct syllable composition the whole way:
This is terminal-live-hangul-mirror.ts working as designed — composed syllables with hold-and-correct steps (e.g. 핫 → 하 + 세 when the batchim moves to the next syllable). The field itself composed 안녕하세요 correctly. No jamo decomposition anywhere.
What that implies
The original report is Galaxy S25 Ultra + Samsung Keyboard; my non-repro is the same code with Gboard. So the decomposition is keyboard-specific, not a general Android issue. The prime suspect is the input props on the session inputs in mobile/app/h/[hostId]/session/[worktreeId].tsx:
live input: autoCorrect={false}, spellCheck={false}, autoComplete="off"
command input: autoCorrect={autocompleteEnabled} (same flags when autocomplete is off)
On Android, React Native maps autoCorrect={false} to a no-suggestions inputType. Samsung Keyboard is known to disable IME composition entirely for such fields (it delivers raw jamo), while Gboard keeps composing. That matches the reported symptom exactly: the field never receives composed syllables, so no downstream handling can fix it.
Worth noting: the repo already documents an adjacent Samsung/Android IME quirk in the same file ("Android caches the IME inputType at mount, so toggling autocomplete must remount"), so a Samsung-specific composition quirk here is consistent with what this surface has hit before.
Suggested fix + verification
A Samsung-safe variant of the input props (keeping suggestions suppressed without tripping Samsung's composition kill — likely dropping the no-suggestions flag on Android for these fields, as terminal-keyboard-type.ts already did for keyboardType), verified on a physical Samsung device — the stock emulator can't run Samsung Keyboard, so I couldn't take it further than this.
@watson-water — if you can still reproduce on the S25, two quick checks would confirm this: (1) does it also happen with Gboard installed on the same device? (2) does Samsung Keyboard's own "text suggestions" toggle change the behavior? If Gboard is clean on your device, that pins it 100% on the inputType/composition interaction.
(iOS report in this thread is likely a separate mechanism — composition there survives autoCorrect={false}, so it deserves its own trace.)
Closing — the Android half is fixed, and we now have real Samsung device evidence.
Fixed by #7011 (4f0a141951, Jul 2) and #7273 (e8c2b79a93, Jul 3), both on main. #7011 is the direct one: the mobile terminal capture field used to send and clear on every TextInput change, which breaks Hangul composition on Android keyboards. It replaced that with a deliberate commit model so composed text is flushed intentionally while ASCII stays immediate. Both landed within two days of this report.
Device confirmation (today): tested on a physical Samsung with Samsung Keyboard — not Gboard — on a build released ~8 hours ago, with predictive text both on and off, and in both Orca keyboard modes (default and live). Hangul composes correctly in every combination. Thanks to @brennanb2025's colleague for running it.
That matters because #7011's own commit message carried the directive "do not claim physical Samsung Keyboard QA without device evidence" — so this is the evidence that was missing.
On the autoCorrect={false} theory from @hanjoonchoe's excellent analysis: it was a well-reasoned hypothesis (Android maps autoCorrect={false} to a no-suggestions inputType, and Samsung Keyboard was suspected to disable composition for such fields). The device test does not support it — composition works with the flag as-is. We built a fix on that theory and are not landing the Android part, since it would change real input behaviour to fix something that no longer reproduces.
The iOS report in this thread is a separate mechanism and is NOT closed by this.@lkjsays reported the same visible symptom on iPhone 17 Pro; that is tracked at #11235. Worth noting we could not reproduce that either on iPhone 14 / iOS 26.5.2 today, with or without a candidate fix — details on #11246. #11235 stays open pending the reporter's iOS version.
@watson-water — if you still see this on your Galaxy S25 Ultra on a current build, please reopen with your One UI version, Android version, and Orca Mobile version, and we will dig in again. Thanks for the original report; it was accurate and it did get fixed.
Activity
lkjsays commentedon Jul 2, 2026
Also reproducing on iOS — iPhone 17 Pro. This is not Android-only; the title/labels (
os:mobile-beta/ Android) undersell the scope.Environment
Symptom — identical to the original report:
안녕하세요ㅇㅏㄴㄴㅕㅇㅎㅏㅅㅔㅇㅛ(decomposed jamo, no syllable composition)So the IME composition/preedit handling issue affects both Android (Samsung Keyboard) and iOS system keyboard, which points to the mobile input field consuming intermediate/per-jamo change events instead of waiting for the composed (committed) text. Likely the same root cause as the terminal-side #7000, but in the chat input surface. +1 on P1.
hanjoonchoe commentedon Jul 18, 2026
I dug into this with a full local repro environment and can narrow the root cause significantly.
Setup
mainmobile/scripts/mock-server.ts(with a locally addedsession.tabs.listhandler so the session screen finishes loading, and a logger onterminal.sendto capture exactly what the app sends)안녕하세요key-by-key into the terminal live input fieldResult: does NOT reproduce with Gboard
The captured
terminal.sendstream shows correct syllable composition the whole way:This is
terminal-live-hangul-mirror.tsworking as designed — composed syllables with hold-and-correct steps (e.g.핫→하+세when the batchim moves to the next syllable). The field itself composed안녕하세요correctly. No jamo decomposition anywhere.What that implies
The original report is Galaxy S25 Ultra + Samsung Keyboard; my non-repro is the same code with Gboard. So the decomposition is keyboard-specific, not a general Android issue. The prime suspect is the input props on the session inputs in
mobile/app/h/[hostId]/session/[worktreeId].tsx:autoCorrect={false},spellCheck={false},autoComplete="off"autoCorrect={autocompleteEnabled}(same flags when autocomplete is off)On Android, React Native maps
autoCorrect={false}to a no-suggestionsinputType. Samsung Keyboard is known to disable IME composition entirely for such fields (it delivers raw jamo), while Gboard keeps composing. That matches the reported symptom exactly: the field never receives composed syllables, so no downstream handling can fix it.Worth noting: the repo already documents an adjacent Samsung/Android IME quirk in the same file ("Android caches the IME inputType at mount, so toggling autocomplete must remount"), so a Samsung-specific composition quirk here is consistent with what this surface has hit before.
Suggested fix + verification
A Samsung-safe variant of the input props (keeping suggestions suppressed without tripping Samsung's composition kill — likely dropping the no-suggestions flag on Android for these fields, as
terminal-keyboard-type.tsalready did forkeyboardType), verified on a physical Samsung device — the stock emulator can't run Samsung Keyboard, so I couldn't take it further than this.@watson-water — if you can still reproduce on the S25, two quick checks would confirm this: (1) does it also happen with Gboard installed on the same device? (2) does Samsung Keyboard's own "text suggestions" toggle change the behavior? If Gboard is clean on your device, that pins it 100% on the inputType/composition interaction.
(iOS report in this thread is likely a separate mechanism — composition there survives
autoCorrect={false}, so it deserves its own trace.)nwparker commentedon Jul 27, 2026
Repro status: env-blocked (no
cannot_reprolabel)Could not device-reproduce: {why}.
Tree:
c3a9a5e8a6. Code review alone is not conclusive for the user-facing failure. Nocannot_reprolabel applied per env-blocked policy.fix(mobile): make the Android autocorrect Off switch mean something a…
brennanb2025 commentedon Jul 29, 2026
Closing — the Android half is fixed, and we now have real Samsung device evidence.
Fixed by #7011 (
4f0a141951, Jul 2) and #7273 (e8c2b79a93, Jul 3), both onmain. #7011 is the direct one: the mobile terminal capture field used to send and clear on everyTextInputchange, which breaks Hangul composition on Android keyboards. It replaced that with a deliberate commit model so composed text is flushed intentionally while ASCII stays immediate. Both landed within two days of this report.Device confirmation (today): tested on a physical Samsung with Samsung Keyboard — not Gboard — on a build released ~8 hours ago, with predictive text both on and off, and in both Orca keyboard modes (default and live). Hangul composes correctly in every combination. Thanks to @brennanb2025's colleague for running it.
That matters because #7011's own commit message carried the directive "do not claim physical Samsung Keyboard QA without device evidence" — so this is the evidence that was missing.
On the
autoCorrect={false}theory from @hanjoonchoe's excellent analysis: it was a well-reasoned hypothesis (Android mapsautoCorrect={false}to a no-suggestionsinputType, and Samsung Keyboard was suspected to disable composition for such fields). The device test does not support it — composition works with the flag as-is. We built a fix on that theory and are not landing the Android part, since it would change real input behaviour to fix something that no longer reproduces.The iOS report in this thread is a separate mechanism and is NOT closed by this. @lkjsays reported the same visible symptom on iPhone 17 Pro; that is tracked at #11235. Worth noting we could not reproduce that either on iPhone 14 / iOS 26.5.2 today, with or without a candidate fix — details on #11246. #11235 stays open pending the reporter's iOS version.
@watson-water — if you still see this on your Galaxy S25 Ultra on a current build, please reopen with your One UI version, Android version, and Orca Mobile version, and we will dig in again. Thanks for the original report; it was accurate and it did get fixed.
fix(mobile): narrow to #4606 — drop the Android autoCorrect omission