Skip to content

[Due for payment 2026-07-13] Wallet - "Choose an account" page shows extra left margin #90182

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: 9.3.69-4
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #87087
Email or phone of affected tester (no customers): josdjnosdjionjsdonjisod@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: User Settings

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to Account > Wallet.
  3. Click Add bank account.
  4. Click Get reimbursed.
  5. Select United States > Next.
  6. Click Add bank account.
  7. Complete Plaid flow.
  8. Reach Choose an account page on ND.

Expected Result:

"Choose an account" page will not have extra left margin.

Actual Result:

"Choose an account" page shows extra left margin.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Image
Bug7150629_1778500689181.22.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. mhawryluk commented on Jun 26, 2026

    @mhawryluk
    Member

    hi, I'm from SWM and can work on this as a follow up to the Consistent checkboxes and radio buttons UI PR

  2. melvin-bot commented on Jul 1, 2026

    @melvin-bot

    Triggered auto assignment to @lakchote, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

  3. added and removed
    ReviewingHas a PR in review
    on Jul 6, 2026
  4. changed the title [-]Wallet - "Choose an account" page shows extra left margin[/-] [+][Due for payment 2026-07-13] Wallet - "Choose an account" page shows extra left margin[/+] on Jul 6, 2026
  5. 10 remaining items

  6. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jul 10, 2026
  7. melvin-bot commented on Jul 12, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  8. melvin-bot commented on Jul 12, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  9. mallenexpensify commented on Jul 14, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @gijoe0295 due $250 via NewDot

    @gijoe0295 plz complete the BZ checklist and tag me in a post once you have. Thx (we'll likely add this to a list of test cases that get run monthly.)

  10. gijoe0295 commented on Jul 14, 2026

    @gijoe0295
    Contributor

    BugZero Checklist:

    • [Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to the comment on the PR: NA. Came from Consistent checkboxes and radio buttons UI #87087 but the author was already aware of and raising the fix PR so no need to comment.
      Link to the comment on the Issue: Same.

    • [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.

      None. This is a simple obvious UI behavior. No need to add a new test case.

  11. JmillsExpensify commented on Jul 14, 2026

    @JmillsExpensify
    Contributor

    $250 approved for @gijoe0295

  12. melvin-bot commented on Jul 17, 2026

    @melvin-bot

    @mallenexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

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

Metadata

Metadata

Labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions