Skip to content

[HOLD for payment 2024-07-17] [$250] Web : Profile section is empty when a workspace is created on the new account #44601

Description

@m-natarajan

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


issue was found when validating #42592
Version Number: 9.0.3-1
Reproducible in staging?: y
Reproducible in production?: n
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. Navigate to https://staging.new.expensify.com/
  2. Log in with a new expensifail account
  3. Click on FAB - New workspace

Expected Result:

The Profile page should be filled with content.

Actual Result:

Occasionally a newly created WS Profile page is empty until the browser is refreshed. Affects Gmail and applause.expensifail.com domains.

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 / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6527003_1719552668233.bandicam_2024-06-28_07-24-55-604.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~018334025bb716d28c
  • Upwork Job ID: 1807790300561756436
  • Last Price Increase: 2024-07-01
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @puneetlath

Activity

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

    @melvin-bot

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

  3. melvin-bot commented on Jun 28, 2024

    @melvin-bot

    Triggered auto assignment to @puneetlath (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.

  4. github-actions commented on Jun 28, 2024

    @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.
  5. m-natarajan commented on Jun 28, 2024

    @m-natarajan
    Author

    @puneetlath FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

  6. m-natarajan commented on Jun 28, 2024

    @m-natarajan
    Author

    We think that this bug might be related to #wave-collect - Release 1

  7. 53 remaining items

  8. melvin-bot commented on Jul 15, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@dukenv0307] The PR that introduced the bug has been identified. Link to the PR:
    • [@dukenv0307] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    • [@dukenv0307] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
    • [@dukenv0307] Determine if we should create a regression test for this bug.
    • [@dukenv0307] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@puneetlath] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  9. puneetlath commented on Jul 16, 2024

    @puneetlath
    Contributor

    Just to make sure I've got it right. @fedirjh was the C and @dukenv0307 was the C+. Is that right?

  10. changed the title [-][HOLD for payment 2024-07-22] [HOLD for payment 2024-07-17] [$250] Web : Profile section is empty when a workspace is created on the new account[/-] [+][HOLD for payment 2024-07-17] [$250] Web : Profile section is empty when a workspace is created on the new account[/+] on Jul 16, 2024
  11. dukenv0307 commented on Jul 17, 2024

    @dukenv0307
    Contributor

    @puneetlath I didn't review this issue. It was fixed somewhere

  12. fedirjh commented on Jul 17, 2024

    @fedirjh
    Contributor
  13. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jul 17, 2024
  14. puneetlath commented on Jul 17, 2024

    @puneetlath
    Contributor

    Ah ok I see @fedirjh. It looks like that PR addressed multiple issues. Which one should we handle payment in?

  15. melvin-bot commented on Jul 17, 2024

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@puneetlath)

    • I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1807790300561756436/hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  16. puneetlath commented on Jul 18, 2024

    @puneetlath
    Contributor

    Looks like @hungvu193 requested payment in the other issue, so I'm going to close this one. Let me know if I'm mistaken and I'll reopen.

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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions