Skip to content

Onboarding - "Add your work Email" button becomes unresponsive if using same Email twice. #60403

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.1.29-0
Reproducible in staging?: Yes
Reproducible in production?: No
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: N/A
Email or phone of affected tester (no customers): ignaciodbellico+902@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome / Windows 10 - Chrome
App Component: Other

Action Performed:

  1. Open the staging.new.expensify.com website.
  2. Sign up with a new account.
  3. On the first step of onboarding modal, add a work Email.
  4. Tap on "Add your work Email" button.
  5. Complete the rest of onboarding modal.
  6. Log out.
  7. Sign up with a new account.
  8. On the first step of onboarding modal, add the same work Email.
  9. Tap on "Add your work Email"
  10. Note that no action is triggered and no error message is displayed.
  11. Change the work Email.
  12. Note that you are redirected to next onboarding step, but a "401" error message is displayed.

Expected Result:

An error message shouuld be displayed when user tries to use the same work Email on a second account.

Actual Result:

Tapping on "Add your work Email" button, doesn´t trigger any action when trying to use an Email that was already used in a different account. Also, when changing Email, user lands on the next onboarding step, but a "401 work account isn´t validated" error message is displayed on the bottom of the screen.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6804592_1744861893923.Company.mp4

View all open jobs on GitHub

Activity

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

    @melvin-bot

    Triggered auto assignment to @twisterdotcom (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 17, 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 17, 2025

    @melvin-bot

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

  5. github-actions commented on Apr 17, 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. allgandalf commented on Apr 17, 2025

    @allgandalf
    Contributor

    same RCA and dupe of #60372

  7. madmax330 commented on Apr 17, 2025

    @madmax330
    Contributor

    Closing then

  8. allgandalf commented on Apr 17, 2025

    @allgandalf
    Contributor

    Tacking this issue here

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.DeployBlockerIndicates it should block deploying the APIEngineeringHourlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions