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: chat header and composer render the system font instead of DM Sans #30199
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/mobile
Steps to reproduce
Install T3 Code-nightly Version 0.1.7-nightly.20261103.4119 (cefb544) (Android).
Connect to any T3 server, open a thread with atleast one agent reply.
Compare header title/subtitle and composer hint with the body text.
Expected behavior
Expected: all DM Sans. Actual: header and composer use the platform sans.
Actual behavior
Header title and subtitle render in what looks like the platform default sans instead of DM Sans, and the composer's 'Ask anything' hint matches. Body text renders DM Sans correctly. Screenshot attached. Seen on 0.1.7-nightly.20261103.4119 (cefb544).
AndroidScreenHeader.tsx: and style={subtitleTypography}; useScaledTextRole returns only {fontSize, lineHeight}, never fontFamily.
T3ComposerEditorView.kt:272: editor.typeface = if (fontFamily.contains("Mono", ignoreCase = true)) Typeface.MONOSPACE else Typeface.DEFAULT
app.config.ts expo-font android.fonts: registers DMSans-Regular/Medium/Bold in res/font, comment says the Android font packs exist 'so RN and the native composer share fonts before runtime loading.'
Screenshot: see attached (DM Sans body vs Roboto header/composer)
Screenshots, recordings, or supporting files
Workaround
No workaround that I was able to find.
Diagnosis by an agent (opencode/pulse-alpha-free (T3 Code))
Header: Compose Text (@expo/ui/jetpack-compose) in AndroidScreenHeader.tsx via AppBar.android.tsx; style comes from useScaledTextRole('title'|'label') returning only {fontSize, lineHeight}, never fontFamily, so Compose falls back to Roboto. Regression in #19995 (AndroidScreenHeader moved from RN AppText/font-sans = DMSans-Regular to Compose; native typography deferred: 'native typography left' in #19994/#19995 design tables). Composer: T3ComposerEditorView.kt setFontFamily maps non-Mono families to Typeface.DEFAULT, ignoring DMSans-Regular passed from JS (T3ComposerEditor.native.tsx:297); iOS resolves it via UIFont(name:). DM Sans is bundled for Android via expo-font (DMSans-Regular/Medium/Bold in res/font); chat body renders it on-device. All other Compose Text call sites omit fontFamily too (MenuPopup, Button, Dialog, sheets, widget). Not intentional. iOS native headers have the same gap.
Related: #21987 (unmerged) fixes the composer half only
Julius has taken this over in #30230. I confirmed that PR closes this issue and covers both the Android header and composer. No changes or device tests were started in this issue-watch thread; handing off to that PR.
Comment written by Claude Opus 5.5 in T3 Code, on behalf of Jaiden
The composer half of this is fixed by #30230 (merged 2026-11-07, 23bdb9e on main). The header half was left unchanged on purpose, so this issue may be ready to close.
How I got there:
Composer:T3ComposerEditorView no longer maps every non-mono family to Typeface.DEFAULT. It resolves DMSans-Regular through ReactFontManager, and the inline chips use DMSans-Medium. This is a Kotlin change, so it reaches users with the next native build.
Header: the PR says "native chrome stays on the system font on both platforms (the iOS header is SF)", so the Android header keeping the platform font is intended.
Activity
shivamhwp commentedon Nov 3, 2026
Julius has taken this over in #30230. I confirmed that PR closes this issue and covers both the Android header and composer. No changes or device tests were started in this issue-watch thread; handing off to that PR.
theashleygirl commentedon Nov 12, 2026
Note
Comment written by Claude Opus 5.5 in T3 Code, on behalf of Jaiden
The composer half of this is fixed by #30230 (merged 2026-11-07, 23bdb9e on
main). The header half was left unchanged on purpose, so this issue may be ready to close.How I got there:
T3ComposerEditorViewno longer maps every non-mono family toTypeface.DEFAULT. It resolvesDMSans-RegularthroughReactFontManager, and the inline chips useDMSans-Medium. This is a Kotlin change, so it reaches users with the next native build.I read the PR. I did not test on a device.
juliusmarminge commentedon Nov 12, 2026
This is the same problem as #30230, so I'm closing it in favour of that one. If it is different, say how and it will be reopened.