[$250] Android-Bank- Search field is auto focused but keyboard does not open in default currency page

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.1.30-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Samsung Galaxy Z Fold 4 / Android 14
App Component: Workspace Settings

Action Performed:

Precondition:

• Log in with Expensifail account.
• Have a workspace with MYR as default currency (or any other currency other than USD, CAD, AUD, GBP, EUR).

1. Launch Expensify app.
2. Go to workspace settings > Workflows.
3. Tap Connect bank account.
4. Tap Update workspace currency.
5. Note that the search field is focused but the keyboard does not open.
6. Go back to workspace settings.
7. Go to Overview > Default currency.
8. Note that the search field is focused and keyboard auto opens.

Expected Result:

In Step 5, the keyboard will auto open as the search field is auto focused.

Actual Result:

In Step 5, the keyboard does not auto open when the search field is auto focused.

This is inconsistent with the keyboard behavior when default currency list is opened from Overview in Step 8.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6806776_1745014898079.Screen_Recording_20250419_061618_Expensify.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021914265783216675056
• Upwork Job ID: 1914265783216675056
• Last Price Increase: 2025-04-21
• Automatic offers:
• brunovjk | Reviewer | 107020729

Issue Owner

Current Issue Owner: @brunovjk

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

[melvin-bot]

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

[garrettmknight]

Demoting, we don't need to block the deploy for this.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021914265783216675056

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @brunovjk (External)

[MrMuzyk]

I am Michał from Callstack - expert contributor group. I’d like to work on this job.

Im also one of the authors of this whole flow this is now behind beta so I have all the needed context.

[garrettmknight]

Go for it!

[melvin-bot]

📣 @brunovjk 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job

[MrMuzyk]

Because there were other issues with the flow and they're all relatively small we've decided to fix all of them in one big follow-up issue - #60633

[brunovjk]

Because there were other issues with the flow and they're all relatively small we've decided to fix all of them in one big follow-up issue - #60633

Not overdue. Working on the fix

[MrMuzyk]

Hey @mitarachim, can you please check if the issue still persists? I wasn't able to reproduce that and frankly it doesn't seem related to changes we've done in global reimbursements flow. Below recording where it works as expected

Screen.Recording.2025-04-24.at.16.00.10.mov

[mitarachim]

Hello @MrMuzyk QA team couldn't reproduce this issue in latest Build 9.1.32-0

Screen_Recording_20250424_220544_Expensify.mp4

[MrMuzyk]

Ok, great :)