Skip to content

Android & iOS - Expense - Description field is not visible when focused#94398

Open
thelullabyy wants to merge 4 commits into
Expensify:mainfrom
thelullabyy:fix/94274
Open

Android & iOS - Expense - Description field is not visible when focused#94398
thelullabyy wants to merge 4 commits into
Expensify:mainfrom
thelullabyy:fix/94274

Conversation

@thelullabyy

@thelullabyy thelullabyy commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #94274
PROPOSAL: NA

Tests

Enable newManualExpenseFlow beta

  1. Launch Expensify app.
  2. Tap + > Create expense > Manual.
  3. Tap Description field.
  4. Description field will be visible when focused.
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

Enable newManualExpenseFlow beta

  1. Launch Expensify app.
  2. Tap + > Create expense > Manual.
  3. Tap Description field.
  4. Description field will be visible when focused.
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Screen.Recording.2026-06-24.at.01.02.03.mov
Android: mWeb Chrome
Screen.Recording.2026-06-24.at.00.57.27.mov
iOS: Native
Screen.Recording.2026-06-24.at.00.37.59.mov
iOS: mWeb Safari
Screen.Recording.2026-06-24.at.00.51.39.mov
MacOS: Chrome / Safari
Screen.Recording.2026-06-24.at.00.52.37.mov

@codecov

codecov Bot commented Jun 24, 2026

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
...onents/MoneyRequestConfirmationFields/Provider.tsx 100.00% <ø> (ø)
...mponents/MoneyRequestConfirmationFields/context.ts 80.00% <ø> (ø)
src/components/MoneyRequestConfirmationList.tsx 94.61% <100.00%> (+0.08%) ⬆️
...RequestConfirmationList/sections/MerchantField.tsx 72.91% <100.00%> (+1.17%) ⬆️
.../components/MoneyRequestConfirmationListFooter.tsx 100.00% <ø> (ø)
...ListWithSections/BaseSelectionListWithSections.tsx 92.70% <100.00%> (+0.15%) ⬆️
...uestConfirmationList/sections/DescriptionField.tsx 74.07% <66.66%> (-1.93%) ⬇️
...lectionList/hooks/useScrollToFocusedInput/index.ts 0.00% <0.00%> (ø)
...List/hooks/useScrollToFocusedInput/index.native.ts 53.12% <53.12%> (ø)
... and 12 files with indirect coverage changes

@thelullabyy

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: 3119a10a07

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@thelullabyy thelullabyy marked this pull request as ready for review June 24, 2026 05:02
@thelullabyy thelullabyy requested review from a team as code owners June 24, 2026 05:02
@melvin-bot melvin-bot Bot requested review from aimane-chnaif and heyjennahay and removed request for a team June 24, 2026 05:02
@melvin-bot

melvin-bot Bot commented Jun 24, 2026

Copy link
Copy Markdown

@aimane-chnaif Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d2f8c50520

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +93 to +96
keyboardListenerRef.current = Keyboard.addListener('keyboardDidShow', () => {
cleanup();
// Give the layout a moment to settle after the keyboard has fully appeared.
scrollTimeoutRef.current = setTimeout(performScroll, CONST.ANIMATION_IN_TIMING);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use a resize-safe keyboard signal on Android

In this app MainActivity runs with android:windowSoftInputMode="adjustResize" (android/app/src/main/AndroidManifest.xml:47) while minSdkVersion is 24, and React Native documents that keyboardDidShow is not fired on Android 10 and below in this mode (https://reactnative.dev/docs/0.85/keyboard#addlistener). On those supported devices this listener path never runs; for the first focus (and any case where isKeyboardShown has not been set yet) the field stays behind the keyboard until the 1s safety timeout fires, so the focused description/merchant field is still not visible when focused. Use the keyboard-controller events already used by withKeyboardState or another Android-safe settled-layout fallback here instead of waiting on RN Keyboard.

Useful? React with 👍 / 👎.

value={displayMerchantValue}
readOnly={didConfirm}
onChangeText={handleMerchantInputChange}
onFocus={() => scrollFocusedInputIntoView?.(inputRef.current)}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to support merchant field as well?
This is single line field and auto-scroll already working as expected.

value={iouComment ?? ''}
readOnly={didConfirm}
onChangeText={handleDescriptionInputChange}
onFocus={() => scrollFocusedInputIntoView?.(inputRef.current)}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it expected multiline input is disabled on mobile?

bug.mov

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants