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
Merge Accounts - Keyboard does not open automatically on Magic Code page. #59783
Version Number: 9.1.24-2 Reproducible in staging?: Yes Reproducible in production?: Unable to check, new feature If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both If this was caught during regression testing, add the test name, ID and link from TestRail:#56911 Email or phone of affected tester (no customers):Ibellicotest+523@gmail.com Issue reported by: Applause Internal Team Device used: Motorola Moto G60/ Android 12 App Component: Other
Action Performed:
Open the Expensify app.
Tap on "Settings" and select "Security"
Tap on "Merge Accounts"
Add an existing account.
Tap on "Next"
Note that keyboard is not automatically opened when reaching the Magic Code page.
Expected Result:
Keyboard should be opened automatically when user reaches the magic code page.
Actual Result:
When reaching the Magic Code page, while on merging accounts process, the keyboard is not automatically displayed and has to be opened manually.
👋 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.
@madmax330@sonialiap this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
Activity
melvin-bot commentedon Apr 8, 2025
Triggered auto assignment to @sonialiap (
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 commentedon Apr 8, 2025
Triggered auto assignment to @madmax330 (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Apr 8, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Apr 8, 2025
👋 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:
thelullabyy commentedon Apr 8, 2025
We should hold for #59087
3 remaining items
melvin-bot commentedon Apr 14, 2025
@madmax330, @sonialiap Eep! 4 days overdue now. Issues have feelings too...
melvin-bot commentedon Apr 16, 2025
@madmax330, @sonialiap Still overdue 6 days?! Let's take care of this!
madmax330 commentedon Apr 16, 2025
Bump @wgsquayson
melvin-bot commentedon Apr 22, 2025
@madmax330 @sonialiap this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
melvin-bot commentedon Apr 22, 2025
@madmax330, @sonialiap Huh... This is 4 days overdue. Who can take care of this?
allroundexperts commentedon Apr 22, 2025
The above PR was merged, and the issue is resolved.
Screen.Recording.2025-04-22.at.5.58.03.PM.mov
sonialiap commentedon Apr 22, 2025
🎉 since #59087 resolved the issue payment will be handled in #54759. Closing this