Voice Control: No Text Input in Terminal View (iPadOS 26.3)

Device: iPad Pro 12.9-inch (5th generation)

OS Version: iPadOS 26.3 (23D127)

App Version: Textastic 10.9.2

Accessibility Feature: Voice Control (hands-free use)

Summary:

Voice Control fails to correctly deliver text input to Textastic's terminal view. This issue has persisted across two iPadOS updates, first observed on January 25, 2026, and remains unresolved as of iPadOS 26.3 (installed February 21, 2026) with Textastic 10.9.2.

Symptom:

Voice Control appears to be active and recognizing commands (as confirmed by testing in standard text fields like Notes), but no text is delivered to Textastic's terminal input field.

Root Cause Analysis:

The issue appears to stem from a conflict between the iPadOS Predictive Text / Composition Engine and how the terminal view handles input:

- When Voice Control processes speech, iPadOS inserts tentative (composition/draft) text into the input field.

- iPadOS then commits the final text, replacing the draft.

- The terminal view does not correctly handle this new two-phase input process, resulting in no visible text being delivered.

Steps to Reproduce:

1. Enable Voice Control via Settings > Accessibility > Voice Control.

2. Open Textastic and launch a terminal session (e.g., via SSH).

3. Use a voice command to dictate a terminal command.

4. Observe that text does not appear in the terminal input field despite Voice Control confirming recognition.

Expected Behavior:

Dictated text and Voice Control aliases should be inserted cleanly into the terminal input field, identical to how they work in Textastic's code editor and other standard text fields (e.g., Notes, Safari address bar).

Impact:

This bug renders Textastic's terminal view completely inaccessible for users who rely on Voice Control for hands-free operation.

Additional Notes:

- Standard text fields, including Textastic's own code editor, handle Voice Control input correctly, confirming the issue is specific to the terminal view's interaction with the iPadOS composition engine.

- The issue did not exist prior to the iPadOS update that introduced the behavior on or around January 25, 2026.