Skip to content

[Bug]: Mobile terminal Korean IME input sends decomposed jamo on Android #7000

Closed

Description

@realitsyourman

Operating system

Other: Android on Galaxy Fold7 with Samsung Keyboard Korean IME

Orca version

  • Repository version observed locally: 1.4.115-rc.0
  • Affected installed mobile build/version: unknown from the device screenshot

Details

Short summary:
On Orca mobile terminal live input, Korean IME composition is broken on Android/Samsung Keyboard. Typing Korean syllables can appear in the terminal as separated consonants/vowels (jamo) instead of composed Hangul syllables.

What happened:

Image

A Korean user on Galaxy Fold7 using Samsung Keyboard sees terminal input like decomposed jamo instead of composed Hangul. The screenshot shows a terminal prompt where Korean text is rendered as separated consonant/vowel characters while typing through Orca mobile terminal live input.

How to reproduce:

  1. Use Orca mobile on Android with Samsung Keyboard set to Korean input.
  2. Open a terminal session and focus the terminal live input surface.
  3. Type a Korean syllable or word such as 한글.
  4. Observe the terminal receives intermediate/decomposed input rather than only the final composed Hangul syllables.

Expected behavior:
The terminal should receive composed Korean text, for example 한글, without sending intermediate IME preedit states such as ㅎ, 하, or decomposed jamo.

Actual behavior:
The live terminal input path sends each TextInput.onChangeText value immediately and clears the hidden capture field immediately after sending. For a Korean IME this can turn a composition sequence like ㅎ → 하 → 한 into terminal bytes for the intermediate states, and the native field reset can interrupt the keyboard composition session.

Source-backed analysis:

  • mobile/app/h/[hostId]/session/[worktreeId].tsx has handleLiveInputChange bound to the live TextInput onChangeText handler.
  • That handler normalizes the incoming text, calls sendLiveTerminalInput(activeHandle, normalizedText) immediately, then clears React state with setLiveInputCapture('') and clears the native input with setNativeProps({ text: '' }).
  • The special-key and submit handlers also send immediately and clear the capture field, so pending IME text is not flushed or protected before terminal control bytes.
  • Existing keyboard-type code intentionally uses keyboardType="default" so non-Latin IMEs are selectable, but that only keeps the keyboard available; it does not preserve composition state through live terminal dispatch.

Proposed fix direction:

  • Add a small, testable terminal live text commit model for mobile input.
  • Keep ASCII terminal typing immediate.
  • Buffer likely IME/non-ASCII live input briefly and send only the settled/committed text.
  • Flush pending text before submit/control keys that should happen after the text.
  • Treat Backspace while text is pending as local IME/preedit editing instead of sending terminal Backspace bytes.
  • Avoid clearing the native capture field while the IME is still composing.

Suggested regression coverage:

  • Model a live input sequence such as ['ㅎ', '하', '한'] and assert the terminal does not receive all intermediates.
  • Assert ASCII live input still sends immediately.
  • Assert Enter flushes pending composed text before carriage return.
  • Assert Backspace with pending IME text does not send a terminal Backspace byte.
  • Run existing mobile terminal input/keyboarding tests and an ASCII terminal smoke test.

Additional QA notes:

  • Primary manual surface: Galaxy Fold7 + Samsung Keyboard Korean IME.
  • Secondary manual surface: Android emulator + Gboard Korean IME if available.
  • This issue should not be considered physically verified until one of those device/emulator runs is captured.

Activity

  1. AmethystLiang commented on Jul 1, 2026

    @AmethystLiang
    Contributor

    thanks for letting us know. will get it resolved ASAP

  2. AmethystLiang commented on Jul 2, 2026

    @AmethystLiang
    Contributor

    will be in next release, usually within 24 hours

  3. added theissue type on Jul 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions