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]: Android composer height flickers when typing "Make it happen. We want adapters" #32700
The filing assistant could not fetch the X recording (HTTP 403); the symptom and reproduction text above are the reporter's description, not an independently reproduced diagnosis.
Related issue
#27650 describes an Android composer oscillating between compact and expanded layouts when a draft is near a wrapping threshold, and is closed. This report supplies another exact triggering draft and a recording. It may be the same underlying issue; without the affected app build, it is not yet established whether this is a regression or an older build missing the fix.
Impact
Visible layout instability during message composition.
Version or commit
Affected Android app version/build and connected server version have not been collected.
Environment
T3 Code Android app. Device model, Android version, keyboard, font scale and display settings have not been collected.
Logs or stack traces
Not collected.
Workaround
Not confirmed for this report. The related #27650 reports that changing the draft length stops its flicker; that workaround has not been verified here.
Same on my side. Android , , T3 Code Android app , Gboard with Vietnamese (Telex) input.
Typing a Vietnamese draft: once it reaches a certain length (near the line-wrap point) the composer starts jumping between heights continuously and the text renders doubled/ghosted while it flickers. Deleting a few characters stops it.
Could you share the installed T3 Code Android version and build number, phone model, Android version, and font/display scaling settings? Please attach the recording directly here as well. For the Vietnamese Gboard case, please include an exact draft that triggers the flicker.
#27682 fixed one Android wrap-boundary loop in native code. The installed build matters because that change requires a new Android binary. We haven't established whether this report is the same bug on an older build or a remaining issue.
Verification update, November 10: current main's mobile code at d1909d68f8a8864d13fcb214c116777a651e6684 did not reproduce the loop on a Simlock Pixel 9 emulator, Android 15 / API 35, portrait 1080×2424, density 2.625, system text-size reported as large, with visible Gboard key presses. The original draft expands once between adapte and adapter and stays expanded for adapters, including while the free Replay provider streams. It does not have to fit and js stays compact; extending that draft past its actual wrap boundary expands once and stays stable. The next main commit, 20bb685e68fda77f60f9324f0db96d4ef06902d2, changes only CI attribution and preserves the tested mobile code.
This is non-reproduction on that configuration, not proof that #27682 fixes this report. Its native rounding fix is present on main and absent from the published 2.2.0 beta-735 source. The reported installed native build remains unknown. Android 17, physical f4/m3 phones, the reporter's scaling settings, and the exact Vietnamese Telex draft remain unverified. No new fix or PR is claimed; the issue stays open pending the remaining reporter details.
Native client fingerprint: 832d41716ea2dfac7350605db3fd07914f87d6ef. APK SHA256: 42955db2e159fbec97f2503af3072af314503f6f91c99b53ad218cce7d186632. The recordings use isolated test data and the free Replay provider.
Original draft typed progressively with Gboard:
main-gboard-keys.mp4
Editing the original wrap boundary during Replay:
main-replay-boundary.mp4
Second reported draft and a longer draft crossing its wrap boundary:
An additional reporter-provided Android recording, 73890.mp4, shows the composer repeatedly switching between the compact single-row layout and the expanded text-plus-toolbar layout while the keyboard stays open. The thread is receiving an agent response. The visible draft is near It does not have to fit and js; changing the final characters moves it between layouts. The recording is 18.62 seconds, 868×1920 at 60 fps.
The reporter confirms they have the latest app offered by Google Play. Their November 9 screenshot shows T3 Code (Beta), beta enrollment, an Open button with no Update button, and "Last updated Oct 28, 2026". It does not expose the installed version code. The public Play listing also reports October 28.
The latest published Android beta mirror, 2.2.0 (735), was published October 29. I inspected android-beta-735:apps/mobile/modules/t3-composer-editor/android/src/main/java/expo/modules/t3composereditor/T3ComposerEditorView.kt: its one-line content width still uses layout.getLineMax(0).toInt(), the downward rounding corrected by #27682 on November 6. Current upstream main at cd87cce900 includes the ceil fix.
This points to the reporter receiving a native app predating the fix, rather than establishing a regression on current main. The screenshot alone does not prove their installed version is build 735. A Google Play native release containing #27682 is needed for affected older builds; a server update or JavaScript OTA cannot supply the Kotlin change.
I could not reproduce against current main because this environment has no Android emulator/device available. The available GitHub connector has no binary attachment upload tool, so the recording and screenshot have not been uploaded. Both are retained locally. No new fix or duplicate PR is claimed.
Investigation by GPT-6.1 Sol in the Codex harness through T3 Code.
Activity
baohappy02 commentedon Nov 8, 2026
Same on my side. Android , , T3 Code Android app , Gboard with Vietnamese (Telex) input.
Typing a Vietnamese draft: once it reaches a certain length (near the line-wrap point) the composer starts jumping between heights continuously and the text renders doubled/ghosted while it flickers. Deleting a few characters stops it.
shivamhwp commentedon Nov 8, 2026
Could you share the installed T3 Code Android version and build number, phone model, Android version, and font/display scaling settings? Please attach the recording directly here as well. For the Vietnamese Gboard case, please include an exact draft that triggers the flicker.
#27682 fixed one Android wrap-boundary loop in native code. The installed build matters because that change requires a new Android binary. We haven't established whether this report is the same bug on an older build or a remaining issue.
Verification update, November 10: current main's mobile code at
d1909d68f8a8864d13fcb214c116777a651e6684did not reproduce the loop on a Simlock Pixel 9 emulator, Android 15 / API 35, portrait 1080×2424, density 2.625, system text-size reported as large, with visible Gboard key presses. The original draft expands once betweenadapteandadapterand stays expanded foradapters, including while the free Replay provider streams.It does not have to fit and jsstays compact; extending that draft past its actual wrap boundary expands once and stays stable. The next main commit,20bb685e68fda77f60f9324f0db96d4ef06902d2, changes only CI attribution and preserves the tested mobile code.This is non-reproduction on that configuration, not proof that #27682 fixes this report. Its native rounding fix is present on main and absent from the published 2.2.0 beta-735 source. The reported installed native build remains unknown. Android 17, physical f4/m3 phones, the reporter's scaling settings, and the exact Vietnamese Telex draft remain unverified. No new fix or PR is claimed; the issue stays open pending the remaining reporter details.
Native client fingerprint:
832d41716ea2dfac7350605db3fd07914f87d6ef. APK SHA256:42955db2e159fbec97f2503af3072af314503f6f91c99b53ad218cce7d186632. The recordings use isolated test data and the free Replay provider.Original draft typed progressively with Gboard:
main-gboard-keys.mp4
Editing the original wrap boundary during Replay:
main-replay-boundary.mp4
Second reported draft and a longer draft crossing its wrap boundary:
main-secondary-draft.mp4
Quarks07 commentedon Nov 9, 2026
An additional reporter-provided Android recording,
73890.mp4, shows the composer repeatedly switching between the compact single-row layout and the expanded text-plus-toolbar layout while the keyboard stays open. The thread is receiving an agent response. The visible draft is nearIt does not have to fit and js; changing the final characters moves it between layouts. The recording is 18.62 seconds, 868×1920 at 60 fps.The reporter confirms they have the latest app offered by Google Play. Their November 9 screenshot shows T3 Code (Beta), beta enrollment, an Open button with no Update button, and "Last updated Oct 28, 2026". It does not expose the installed version code. The public Play listing also reports October 28.
The latest published Android beta mirror, 2.2.0 (735), was published October 29. I inspected
android-beta-735:apps/mobile/modules/t3-composer-editor/android/src/main/java/expo/modules/t3composereditor/T3ComposerEditorView.kt: its one-line content width still useslayout.getLineMax(0).toInt(), the downward rounding corrected by #27682 on November 6. Current upstream main atcd87cce900includes theceilfix.This points to the reporter receiving a native app predating the fix, rather than establishing a regression on current main. The screenshot alone does not prove their installed version is build 735. A Google Play native release containing #27682 is needed for affected older builds; a server update or JavaScript OTA cannot supply the Kotlin change.
I could not reproduce against current main because this environment has no Android emulator/device available. The available GitHub connector has no binary attachment upload tool, so the recording and screenshot have not been uploaded. Both are retained locally. No new fix or duplicate PR is claimed.
Investigation by GPT-6.1 Sol in the Codex harness through T3 Code.
bioshazard commentedon Nov 9, 2026
version 2.2.0
com.t3tools.t3code
Android 17
Build CP3A.261005.005
juliusmarminge commentedon Nov 12, 2026
This is the same problem as #27650, so I'm closing it in favour of that one. If it is different, say how and it will be reopened.