Skip to content

Merge Accounts - Keyboard does not open automatically on Magic Code page. #59783

Closed

Description

@jponikarchuk

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

  1. Open the Expensify app.
  2. Tap on "Settings" and select "Security"
  3. Tap on "Merge Accounts"
  4. Add an existing account.
  5. Tap on "Next"
  6. 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.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on Apr 8, 2025
  2. melvin-bot commented on Apr 8, 2025

    @melvin-bot

    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.

  3. melvin-bot commented on Apr 8, 2025

    @melvin-bot

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

  4. melvin-bot commented on Apr 8, 2025

    @melvin-bot

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

  5. github-actions commented on Apr 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.
  6. thelullabyy commented on Apr 8, 2025

    @thelullabyy
    Contributor

    We should hold for #59087

  7. 3 remaining items

  8. melvin-bot commented on Apr 14, 2025

    @melvin-bot

    @madmax330, @sonialiap Eep! 4 days overdue now. Issues have feelings too...

  9. melvin-bot commented on Apr 16, 2025

    @melvin-bot

    @madmax330, @sonialiap Still overdue 6 days?! Let's take care of this!

  10. madmax330 commented on Apr 16, 2025

    @madmax330
    Contributor
  11. moved this to Bugs and Follow Up Issues in #expensify-bugson Apr 18, 2025
  12. melvin-bot commented on Apr 22, 2025

    @melvin-bot

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

  13. melvin-bot commented on Apr 22, 2025

    @melvin-bot

    @madmax330, @sonialiap Huh... This is 4 days overdue. Who can take care of this?

  14. allroundexperts commented on Apr 22, 2025

    @allroundexperts
    Contributor

    The above PR was merged, and the issue is resolved.

    Screen.Recording.2025-04-22.at.5.58.03.PM.mov
  15. sonialiap commented on Apr 22, 2025

    @sonialiap
    Contributor

    🎉 since #59087 resolved the issue payment will be handled in #54759. Closing this

  16. moved this from Bugs and Follow Up Issues to Done in #expensify-bugson Apr 22, 2025
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.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions