Android - Composer is blocked by keyboard after changing payment method or backgrounding app

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.79-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team
Component: Chat Report View

Action Performed:

Bug 1:

1. Launch ND or hybrid app
2. Go to workspace chat
3. Submit an expense to the workspace chat
4. After submitting the expense, the composer will remain focused and keyboard is not opened. Do not tap on the composer to bring up the keyboard
5. Tap on the payment dropdown button
6. Tap Pay with Expensify

Bug 2:

1. Launch ND or hybrid app
2. Open any chat
3. Background the app
4. Open the app

Expected Result:

When keyboard opens after changing payment button or backgrounding app, the chat will move up to give space for the keyboard and it will not block the composer

Actual Result:

When keyboard opens after changing payment button or backgrounding app, the chat does not move up and the composer is blocked by the keyboard

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6703157_1735331012810.bug_1.mp4

Bug6703157_1735331012816.BUG_2.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @neil-marcellini (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[parasharrajat]

May be related to #51172

[neil-marcellini]

That sounds likely, thanks @parasharrajat. I will see if I can test out a revert on Browserstack. If not I'll request someone who has recently built Android to try it out.

[jasperhuangg]

@neil-marcellini It isn't a straight revert sadly. If you want to do an AdHoc build I have an Android device we can use to test the revert.