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 contributors@expensify.com 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): applausetester+909608@applause.expensifail.com
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.

[christianwen]

I raised the PR to fix the first issue: #54651. For the second one, I can't reproduce on latest main

[melvin-bot]

📣 @christianwen! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[Beamanator]

@christianwen - please fill out your contributor details like it's stated above 🙏

Also @christianwen / @DylanDylann the fix should now be in staging! Anyone free to test?

[marcaaron]

+1 on the above question. Seems like this is 1/2 remaining deploy blockers. Maybe QA can help test if they are around.

[isagoico]

We tried reproducing the issue on the build 9.0.79-5 and the second bug is still reproducible. Video below:

Screenrecorder-2024-12-31-09-01-03-631.mp4

[Beamanator]

@christianwen are you still looking at the above? Please do since this is a deploy blocker 🙏

[puneetlath]

I'm going to demote this since the remaining blocker requires killing and reopening the app, which seems less urgent to fix.

[melvin-bot]

Triggered auto assignment to @garrettmknight (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[christianwen]

@Beamanator I can't reproduce the second bug, what about you @DylanDylann?

[DylanDylann]

I also can't reproduce on 9.0.80-6

Screen.Recording.2025-01-04.at.05.39.26.mov

[DylanDylann]

@isagoico Could you help to try again and provide information about your device? Thanks

[isagoico]

Issue is still reproducible on our side. Device details: Realme C67, Android 14
Here's another reproduction video:

screen-20250106-192316.mp4

[DylanDylann]

@christianwen Could you please check this one?

[christianwen]

@DylanDylann I'm trying to reproduce, will give an update by EOD

[melvin-bot]

@garrettmknight, @neil-marcellini Whoops! This issue is 2 days overdue. Let's get this updated quick!