fix(android): keep the tab bar under the keyboard and load pager-view header fonts OK-63557 OK-63273

[huhuanming]

Summary

• tab-view (Android), OK-63557: the bottom tab bar stays under the soft keyboard instead of rising above it. A new Android-only prop, ignoreKeyboardInsets (default true), switches back to the "follow the keyboard" behavior from JS.
• pager-view (Android), OK-63273: the native Market headers load fontFamily from the app's bundled fonts through ReactFontManager, so Roobert-Medium no longer falls back to the system font. This upstreams the patch-package patch app-monorepo carried; no props change.
• Released as 3.0.140 (tab bar) and 3.0.141 (fonts), both tagged latest.

Commit	Change
b6122250f	fix(android): keep the bottom tab bar under the keyboard
e47d44c45	feat(tab-view): add ignoreKeyboardInsets
c41feab75	chore: bump packages to 3.0.140
6cf822dc7	fix(pager-view): load Android native header fonts from app assets
6e519a308	chore: bump packages to 3.0.141

1. Tab bar rises with the keyboard (OK-63557)

Root cause

1. The window is in adjustResize. app-monorepo declares adjustPan on MainActivity, but react-native-keyboard-controller's useResizeMode() switches the window to SOFT_INPUT_ADJUST_RESIZE whenever KeyboardAwareScrollView, KeyboardStickyView or a keyboard animation hook is mounted. The Swap container uses KeyboardAwareScrollView; dumpsys window shows sim={adjust=resize} once the Trade tab loads.
2. Under adjustResize the compat system-window inset includes the IME. InsetsState.calculateInsets adds ime() to compatInsetsTypes only for SOFT_INPUT_ADJUST_RESIZE.
3. Material pads the bar with that inset. BottomNavigationView (Material 1.14.0-alpha05) applies padding.bottom += insets.getSystemWindowInsetBottom().
4. The scene shrinks. ReactBottomNavigationView is a vertical LinearLayout, so the taller bar shrinks the scene and puts its items directly on the keyboard. onTabBarMeasured also reported the inflated height to JS, which breaks Page.Footer's max(keyboardHeight - tabBarHeight, 0) offset.

Change

• ExtendedBottomNavigationView installs its own ViewCompat.setOnApplyWindowInsetsListener. It pads with systemBars() | displayCutout() and keeps the RTL-aware start/end handling Material had.
• ignoreKeyboardInsets (WithDefault<boolean, true>, Android only). When set to false, the IME inset, read explicitly via ime(), is combined with the navigation bar inset through maxOf(), independent of ignoreBottomInsets. The value lives in JS, so it can change without a native release.
• setIgnoreBottomInsets toggles a flag and re-requests insets. Passing false used to clear the listener and drop the navigation bar padding.
• ReactBottomNavigationView re-applies both inset flags when onConfigurationChanged recreates the bar.

Verification

app-monorepo x with these files in node_modules, shell rebuilt with dev-shell --shell local. API 35 emulator, Trade tab, Swap From amount focused, Gboard docked number pad (IME inset top y=1505).

Build / prop	No keyboard	Number pad up
before (3.0.139)	0,2190-1080,2400	0,1486-1080,2400: bar sits on the keyboard
prop omitted (default true)	0,2190-1080,2400	0,2190-1080,2400: covered by the keyboard
ignoreKeyboardInsets={false}	0,2190-1080,2400	0,1486-1080,2400: rises above the keyboard
prop removed at runtime, keyboard open	—	back to 0,2190-1080,2400

• Codegen: setIgnoreKeyboardInsets is generated with a missing value mapped to true, and the C++ props default is bool ignoreKeyboardInsets{true}.
• Other behavior: dismissing the keyboard causes no jump; no new crash or warning in logcat.
• Not covered:
  • ignoreKeyboardInsets={false} on adjustPan screens.
  • API ≤ 29.
  • The onConfigurationChanged recreation path, which app-monorepo skips because it sets barTintColor.
  • RTL, landscape and tablets, and physical devices.

2. Pager-view native header fonts (OK-63273)

Root cause

CollapsiblePagerNativeHeaders.kt resolved fontFamily with Typeface.create(fontFamily, NORMAL) for the native tab bar buttons, category items and column labels. On Android that only finds system font families, so the bundled Roobert-Medium silently fell back to the system font.

iOS was already correct. [UIFont fontWithName:size:] finds Roobert because the fonts are listed in UIAppFonts, bundled as resources, and their PostScript names match (Roobert-Regular / -Medium / -SemiBold / -Bold).

Change

All three call sites use ReactFontManager.getInstance().getTypeface(fontFamily, NORMAL, context.assets), the Android counterpart of fontWithName:. The fontFamily prop and its sans-serif-medium default are unchanged, and no props are added on either platform.

• It is the standard React Native font lookup. React Native Text uses it (ReactTypefaceUtils), and so do react-native-screens (native tabs), react-native-svg, lottie-react-native and this repo's tab-view.
• Its worst case is the old behavior. It checks registered custom fonts first, then assets/fonts/<family>.ttf|otf, catching the RuntimeException for a missing asset. Only then does it fall back to Typeface.create. Results are cached per family and style.

Verification

app-monorepo Market home on the API 35 emulator, with the patch removed. I built once with the old file and once with this change, then compared the native tab label ink widths with CoreText's width for Roobert-Medium at 42px (16sp × 2.625):

Label	Roobert-Medium	Before (Typeface.create)	After (ReactFontManager)
Favorites	168.6	164	169
Trending	164.6	159	164
Stocks	126.8	124	126
Robinhood	204.8	195	204

The compiled class calls ReactFontManager.getTypeface(String, int, AssetManager). On current app-monorepo x, Android renders the Stocks chips with the JS selector (app-monorepo #13495), so the native sub header, which uses the same helper, is not shown there.

Overlap with #104

#104 (Android floating tab bar) edits the same tab-view files: RCTTabView.kt, RCTTabViewManager.kt, TabView.tsx and TabViewNativeComponent.ts. It adds the same ViewCompat / WindowInsetsCompat imports, new props next to ignoreBottomInsets, setIgnoreBottomInsets(...) calls when switching styles, and manual bottomNavigation padding. Whichever PR lands second needs a rebase. With this change, #104's setIgnoreBottomInsets(false) keeps the inset listener instead of clearing it. Its manual setPadding should be checked against the listener, which re-applies base padding plus the enabled insets on every inset pass.

Release

Both versions were published from this branch with the latest dist-tag, and each run verified all 40 packages on the registry. I also compared the downloaded tarballs with the emulator-tested sources: tab-view RCTTabView.kt / RCTTabViewManager.kt for 3.0.140, and pager-view CollapsiblePagerNativeHeaders.kt for 3.0.141. They are byte-identical.

Version	Commit	Publish run	app-monorepo pin bump
3.0.140	c41feab75	35111444837	OneKeyHQ/app-monorepo#13496 (merged)
3.0.141	6e519a308	35118784967	OneKeyHQ/app-monorepo#13499, which also removes the pager-view patch

Jira: https://onekeyhq.atlassian.net/browse/OK-63557, https://onekeyhq.atlassian.net/browse/OK-63273

🤖 Generated with Claude Code

[sidmorizon]

@codex review

[sidmorizon]

@codex security review

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	🔄 Running since 2026-09-16T16:36:47.387379Z	6e519a3	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Hooray!

Reviewed commit: 6e519a3080

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[sidmorizon]

Claude review session: https://claude.ai/code/session_01BRDSb9U47m68vWNXZLXogJ