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
Android - Composer is blocked by keyboard after changing payment method or backgrounding app #54629
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:
Launch ND or hybrid app
Go to workspace chat
Submit an expense to the workspace chat
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
Tap on the payment dropdown button
Tap Pay with Expensify
Bug 2:
Launch ND or hybrid app
Open any chat
Background the app
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 evidenceBug6703157_1735331012810.bug_1.mp4Bug6703157_1735331012816.BUG_2.mp4
👋 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:
Identify the pull request that introduced this issue and revert it.
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.
📣 @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:
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.
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.
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>
Hi there! Yes, apologies that I missed to update here. We were able to reproduce the bug following the steps for the 1st bug. We tried using the build from this PR
Activity
melvin-bot commentedon Dec 27, 2024
Triggered auto assignment to @neil-marcellini (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Dec 27, 2024
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Dec 27, 2024
👋 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:
parasharrajat commentedon Dec 27, 2024
May be related to #51172
neil-marcellini commentedon Dec 27, 2024
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 commentedon Dec 27, 2024
@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.
zzz0108 commentedon Dec 30, 2024
I raised the PR to fix the first issue: #54651. For the second one, I can't reproduce on latest main
melvin-bot commentedon Dec 30, 2024
📣 @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:
Format:
17 remaining items
melvin-bot commentedon Jan 8, 2025
@garrettmknight, @neil-marcellini Whoops! This issue is 2 days overdue. Let's get this updated quick!
zzz0108 commentedon Jan 8, 2025
I can reproduce when follow these steps here
zzz0108 commentedon Jan 8, 2025
The PR is up @DylanDylann
DylanDylann commentedon Jan 10, 2025
@isagoico Could you please test this bug on this build?
melvin-bot commentedon Jan 10, 2025
@garrettmknight, @neil-marcellini Eep! 4 days overdue now. Issues have feelings too...
melvin-bot commentedon Jan 20, 2025
@garrettmknight, @neil-marcellini, @DylanDylann Huh... This is 4 days overdue. Who can take care of this?
garrettmknight commentedon Jan 20, 2025
@isagoico Did you get a chance to test that build?
isagoico commentedon Jan 21, 2025
Hi there! Yes, apologies that I missed to update here. We were able to reproduce the bug following the steps for the 1st bug. We tried using the build from this PR
Here's the video:
screen-20250110-185017.mp4
Device: Realme C67, Android 14
DylanDylann commentedon Jan 21, 2025
I can't reproduce on the latest main. @isagoico Could you try again on the staging for both bugs mentioned on the original post?
Screen.Recording.2025-01-21.at.15.49.16.mov
The build here is the fix for second bug
melvin-bot commentedon Jan 28, 2025
@garrettmknight, @neil-marcellini, @DylanDylann Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
isagoico commentedon Jan 29, 2025
Both issues are not reproducible anymore on Stg and Prod. Videos here:
bug.1.mp4
bug.2.mp4
Device: Pixel 8 aOS 14
DylanDylann commentedon Jan 29, 2025
@isagoico So let's close this issue
isagoico commentedon Jan 29, 2025
Copy that!