Skip to content

[HOLD for payment 2023-10-31] Web - Login - Chat report loads infinitely with /undefined URL when logging in with a new account #30126

Closed

Description

@lanitochka17

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: 1.3.88-3

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

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

Action Performed:

  1. Go to staging.new.expensify.com
  2. Sign up and log in

Expected Result:

Chat will open

Actual Result:

The chat report loads infinitely with /undefined URL

Workaround:

Unknown

Platforms:

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

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS : Chrome
  • MacOS: Desktop

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Bug6245637_1697904738471.bandicam_2023-10-21_19-39-08-874__1_.1.mp4
MacOS: Desktop

View all open jobs on GitHub

Activity

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

    @melvin-bot

    Triggered auto assignment to @MitchExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. melvin-bot commented on Oct 21, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  4. OSBotify commented on Oct 21, 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.
  5. melvin-bot commented on Oct 21, 2023

    @melvin-bot

    Triggered auto assignment to @Li357 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  6. thienlnam commented on Oct 21, 2023

    @thienlnam
    Contributor

    Taking this over so we can deploy monday morning

  7. 31 remaining items

  8. melvin-bot commented on Oct 25, 2023

    @melvin-bot
  9. MitchExpensify commented on Oct 25, 2023

    @MitchExpensify
    Contributor

    Reassigning as I'm OOO

  10. sophiepintoraetz commented on Oct 25, 2023

    @sophiepintoraetz
    Contributor

    @MitchExpensify - can you please summarise what needs to happen here?

  11. MitchExpensify commented on Oct 28, 2023

    @MitchExpensify
    Contributor

    We'll just need to do a payout of the C+ that reviewed the fix (@allroundexperts)

    Just this on the 31st, I'll take this back as I'm back from vacay now 👍

  12. melvin-bot commented on Nov 1, 2023

    @melvin-bot

    @thienlnam, @MitchExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  13. thienlnam commented on Nov 1, 2023

    @thienlnam
    Contributor

    Looks like tis is ready for payment!

  14. MitchExpensify commented on Nov 3, 2023

    @MitchExpensify
    Contributor

    Payment summary:

  15. JmillsExpensify commented on Nov 13, 2023

    @JmillsExpensify
    Contributor

    $500 payment approved for @allroundexperts based on comment above.

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions