Skip to content

[Due for payment 2025-09-09] [$250] mWeb-Keyboard appear briefly when press device back button on selector #68191

Closed

Description

@mitarachim

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: v9.1.91-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #67579
Email or phone of affected tester (no customers): ndk.2303+approver@gmail.com
Issue reported by: Applause Internal Team
Device used: Android 16 / Pixel 7A/ Chrome
App Component: User Settings

Action Performed:

  1. Open https://staging.new.expensify.com/
  2. Navigate to /enable-payments or add bank account flow
  3. Tap on 'State'
  4. Close the keyboard
  5. Tap on device back button

Expected Result:

When tap on device back button, the previous page button will be shown smoothly

Actual Result:

When tap on device back button, the keyboard appears briefly, Can be reproducible with Swipe navigation

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6911126_1754632285324.Keyboard_appear_briefly.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021953838902589004264
  • Upwork Job ID: 1953838902589004264
  • Last Price Increase: 2025-08-15
  • Automatic offers:
    • dominictb | Reviewer | 108472261
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @Christinadobrzyn

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Aug 8, 2025
  2. github-actions commented on Aug 8, 2025

    @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.
  3. melvin-bot commented on Aug 8, 2025

    @melvin-bot

    Triggered auto assignment to @Christinadobrzyn (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.

  4. melvin-bot commented on Aug 8, 2025

    @melvin-bot

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

  5. melvin-bot commented on Aug 8, 2025

    @melvin-bot

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

  6. 48 remaining items

  7. melvin-bot commented on Sep 2, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  8. melvin-bot commented on Sep 2, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.0-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-09-09. 🎊

    For reference, here are some details about the assignees on this issue:

  9. melvin-bot commented on Sep 2, 2025

    @melvin-bot

    @dominictb @Christinadobrzyn The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  10. Christinadobrzyn commented on Sep 4, 2025

    @Christinadobrzyn
    Contributor

    @dominictb please let us know about a regression test. TY!

  11. dominictb commented on Sep 5, 2025

    @dominictb
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: https://github.com/Expensify/App/pull/55157/files#r2324542782

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: NA

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue: https://github.com/Expensify/Expensify/issues/545695

    Regression Test Proposal

    Test:

    1. Go to Profile > Date of birth
    2. Tap on 'State' (or 'Year' field within the Date of Birth section).
    3. Close the keyboard
    4. Tap on device back button
    5. When tap on device back button, keyboard won't show briefly

    Do we agree 👍 or 👎

  12. Christinadobrzyn commented on Sep 9, 2025

    @Christinadobrzyn
    Contributor

    Payment summary - #68191 (comment)
    Regression test - #68191 (comment)

    Done! Closing

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions