Skip to content

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

Closed

Description

@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

Issue OwnerCurrent Issue Owner: @DylanDylann

Activity

  1. melvin-bot commented on Dec 27, 2024

    @melvin-bot

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

  2. melvin-bot commented on Dec 27, 2024

    @melvin-bot

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

  3. github-actions commented on Dec 27, 2024

    @github-actions
    Contributor

    👋 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.
  4. parasharrajat commented on Dec 27, 2024

    @parasharrajat
    Member

    May be related to #51172

  5. neil-marcellini commented on Dec 27, 2024

    @neil-marcellini
    Contributor

    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.

  6. jasperhuangg commented on Dec 27, 2024

    @jasperhuangg
    Contributor

    @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.

  7. zzz0108 commented on Dec 30, 2024

    @zzz0108
    Contributor

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

  8. melvin-bot commented on Dec 30, 2024

    @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.
      Screen Shot 2022-11-16 at 4 42 54 PM
      Format:
    Contributor details
    Your Expensify account email: <REPLACE EMAIL HERE>
    Upwork Profile Link: <REPLACE LINK HERE>
    
  9. 17 remaining items

  10. melvin-bot commented on Jan 8, 2025

    @melvin-bot

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

  11. zzz0108 commented on Jan 8, 2025

    @zzz0108
    Contributor

    I can reproduce when follow these steps here

  12. zzz0108 commented on Jan 8, 2025

    @zzz0108
    Contributor

    The PR is up @DylanDylann

  13. DylanDylann commented on Jan 10, 2025

    @DylanDylann
    Contributor

    @isagoico Could you please test this bug on this build?

  14. melvin-bot commented on Jan 10, 2025

    @melvin-bot

    @garrettmknight, @neil-marcellini Eep! 4 days overdue now. Issues have feelings too...

  15. melvin-bot commented on Jan 20, 2025

    @melvin-bot

    @garrettmknight, @neil-marcellini, @DylanDylann Huh... This is 4 days overdue. Who can take care of this?

  16. garrettmknight commented on Jan 20, 2025

    @garrettmknight
    Contributor

    @isagoico Did you get a chance to test that build?

  17. isagoico commented on Jan 21, 2025

    @isagoico

    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

  18. DylanDylann commented on Jan 21, 2025

    @DylanDylann
    Contributor

    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

  19. melvin-bot commented on Jan 28, 2025

    @melvin-bot

    @garrettmknight, @neil-marcellini, @DylanDylann Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  20. isagoico commented on Jan 29, 2025

    @isagoico

    Both issues are not reproducible anymore on Stg and Prod. Videos here:

    bug.1.mp4
    bug.2.mp4

    Device: Pixel 8 aOS 14

  21. DylanDylann commented on Jan 29, 2025

    @DylanDylann
    Contributor

    @isagoico So let's close this issue

  22. isagoico commented on Jan 29, 2025

    @isagoico

    Copy that!

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions