Skip to content

Unable to sign in with email/password/2fa on staging web #11305

Closed

Description

@cead22

To reproduce you must have an account with 2fa required

  • Go to staging.new.expensify.com
  • Enter your email
  • Enter your password

What actually happens:

An error is shown saying you must login with email and password

image

What I expect to happen:

The 2FA field should be visible and there should not be any error

Platforms:

  • Staging web

Activity

  1. melvin-bot commented on Sep 26, 2022

    @melvin-bot

    Triggered auto assignment to @tgolen (Demolition), see https://stackoverflow.com/c/expensify/questions/8099 for more details.

  2. OSBotify commented on Sep 26, 2022

    @OSBotify
    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.
  3. melvin-bot commented on Sep 26, 2022

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  4. tgolen commented on Sep 26, 2022

    @tgolen
    Contributor

    @MonilBhavsar Is this possibly related to your change in https://github.com/Expensify/Web-Expensify/pull/34757 ? I see that is the most recent change in this area. Did it also need a front-end change?

  5. self-assigned this
    on Sep 27, 2022
  6. MonilBhavsar commented on Sep 27, 2022

    @MonilBhavsar
    Contributor

    This should be related to #10811. Co-assigning and looking into it

  7. MonilBhavsar commented on Sep 27, 2022

    @MonilBhavsar
    Contributor

    Requested a CP here https://expensify.slack.com/archives/C07J32337/p1664288355879469
    It works now on staging.
    But we need to CP it first to production before deploying App. So not removing DeployBlocker label.

    Sorry for not noticing it earlier 🙇

  8. removed their assignment
    on Sep 27, 2022
  9. danieldoglas commented on Sep 27, 2022

    @danieldoglas
    Contributor

    @MonilBhavsar just to confirm but is it possible that this is related to https://github.com/Expensify/Expensify/issues/230643?

  10. roryabraham commented on Sep 27, 2022

    @roryabraham
    Contributor

    I was never able to reproduce this, but it looks like https://github.com/Expensify/Web-Expensify/pull/34964 was CP'd to production. Can we determine if we are good to close this out or not?

  11. cead22 commented on Sep 27, 2022

    @cead22
    ContributorAuthor

    I just tested this on staging and it's working fine

  12. MonilBhavsar commented on Sep 28, 2022

    @MonilBhavsar
    Contributor

    @MonilBhavsar just to confirm but is it possible that this is related to https://github.com/Expensify/Expensify/issues/230643?

    I don't think so as we haven't updated the olddot code.

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions