Skip to content

[HOLD for payment 2023-02-08] [HOLD for payment 2023-02-07] Web - Login - A console error after login in any account #14666

Closed

Description

@kbecciv

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Go to URL https://staging.new.expensify.com/
  2. Enter the email on the email field and continue
  3. Enter the password on the password field and continue

Expected Result:

No console error after login in any account

Actual Result:

A console error after login in any account

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.2.62.0

Reproducible in staging?: Yes

Reproducible in production?: No

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

image (4)

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Activity

  1. locked and limited conversation to collaborators on Jan 30, 2023
  2. OSBotify commented on Jan 30, 2023

    @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. francoisl commented on Jan 30, 2023

    @francoisl
    Contributor

    I can reproduce, looks like it's coming from this PR. Look into a fix now.

  4. added
    ReviewingHas a PR in review
    and removed
    ReviewingHas a PR in review
    on Jan 30, 2023
  5. thienlnam commented on Jan 31, 2023

    @thienlnam
    Contributor

    PR for fix here: #14663

  6. thienlnam commented on Jan 31, 2023

    @thienlnam
    Contributor
  7. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jan 31, 2023
  8. changed the title [-]Web - Login - A console error after login in any account[/-] [+][HOLD for payment 2023-02-07] Web - Login - A console error after login in any account[/+] on Jan 31, 2023
  9. unlocked this conversation on Jan 31, 2023
  10. melvin-bot commented on Jan 31, 2023

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  11. melvin-bot commented on Jan 31, 2023

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.62-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2023-02-07. 🎊

    After the hold period, please check if any of the following need payment for this issue, and if so check them off after paying:

    • External issue reporter
    • Contributor that fixed the issue
    • Contributor+ that helped on the issue and/or PR

    As a reminder, here are the bonuses/penalties that should be applied for any External issue:

    • Merged PR within 3 business days of assignment - 50% bonus
    • Merged PR more than 9 business days after assignment - 50% penalty
  12. changed the title [-][HOLD for payment 2023-02-07] Web - Login - A console error after login in any account[/-] [+][HOLD for payment 2023-02-08] [HOLD for payment 2023-02-07] Web - Login - A console error after login in any account[/+] on Feb 1, 2023
  13. melvin-bot commented on Feb 1, 2023

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.63-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2023-02-08. 🎊

    After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

    • External issue reporter
    • Contributor that fixed the issue
    • Contributor+ that helped on the issue and/or PR

    As a reminder, here are the bonuses/penalties that should be applied for any External issue:

    • Merged PR within 3 business days of assignment - 50% bonus
    • Merged PR more than 9 business days after assignment - 50% penalty
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions