Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[HOLD for payment 2024-06-05] [UX Reliability] [$250] Expense - LHN shows blank row when opening transaction thread #42096

Closed
2 of 6 tasks
lanitochka17 opened this issue May 13, 2024 · 26 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor

Comments

@lanitochka17
Copy link

lanitochka17 commented May 13, 2024

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.4.73-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: N/A
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com, go offline
  2. Submit two expenses to a user with no chat history
  3. Click on the IOU preview in the main chat
  4. Click on the first expense

Expected Result:

LHN will display the transaction thread of the first expense

Actual Result:

LHN displays a blank row for the transaction thread of the first expense

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

Add any screenshot/video evidence

Bug6479555_1715616252998.20240513_235920.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01a437d649825676f1
  • Upwork Job ID: 1790367877808570368
  • Last Price Increase: 2024-05-14
  • Automatic offers:
    • DylanDylann | Contributor | 0
Issue OwnerCurrent Issue Owner: @twisterdotcom
@lanitochka17 lanitochka17 added DeployBlockerCash This issue or pull request should block deployment DeployBlocker Indicates it should block deploying the API labels May 13, 2024
@github-actions github-actions bot added the Hourly KSv2 label May 13, 2024
Copy link

melvin-bot bot commented May 13, 2024

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open Staging deploy checklist to see the list of PRs included in this release, then work quickly on the following:

  1. If you find which PR caused the issue/bug, you can reassign it to the person responsible for it.
    • If the author is OOO or won’t get online before the daily deploy is due, you are responsible for finding the best fix/path forward. Don’t hesitate to ask for help!
  2. Try to reproduce the issue, if the bug is on production, remove the DeployBlocker label but stay assigned to fix it (or find out which PR broke it to get help from the author).
    • You can adjust the urgency of the issue to better represent the gravity of the bug.
    • If the issue is super low priority, feel free to un-assign yourself.
    • Be careful with PHP warnings, sometimes it is more complex than just adding a null coalescing operator as they might be uncovering some bigger bug.
    • If it was a one-off issue that requires no action (for example, Bedrock was down or it is a duplicated issue), you can close it.

Remember rule #2: Never un-assign yourself from a real DeployBlocker unless you are 100% sure someone else is assigned and will take care of it.

Copy link
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.

Copy link

melvin-bot bot commented May 13, 2024

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

@thienlnam thienlnam removed the DeployBlocker Indicates it should block deploying the API label May 13, 2024
@thienlnam
Copy link
Contributor

Can be produced offline so it's probably not an API blocker

@thienlnam
Copy link
Contributor

Thought it might have been #40336 but I can still reproduce with it - it requires that you are offline

@thienlnam
Copy link
Contributor

thienlnam commented May 13, 2024

I can still reproduce with #41821 so it isn't that one either

@Beamanator
Copy link
Contributor

Hmm confirmed this isn't happening in prod 👍

@Beamanator Beamanator added the External Added to denote the issue can be worked on by a contributor label May 14, 2024
@melvin-bot melvin-bot bot changed the title Expense - LHN shows blank row when opening transaction thread [$250] Expense - LHN shows blank row when opening transaction thread May 14, 2024
Copy link

melvin-bot bot commented May 14, 2024

Job added to Upwork: https://www.upwork.com/jobs/~01a437d649825676f1

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label May 14, 2024
Copy link

melvin-bot bot commented May 14, 2024

Triggered auto assignment to Contributor-plus team member for initial proposal review - @ikevin127 (External)

@Beamanator
Copy link
Contributor

I believe this can be external, since this pretty much is only happening when offline 🤔

@ishpaul777
Copy link
Contributor

i think this one is offending PR #41898

@Beamanator
Copy link
Contributor

Beamanator commented May 14, 2024

@ishpaul777 can you please explain why you think so? :D 🙏

@ishpaul777
Copy link
Contributor

there's a View added instead of returning null here - https://github.com/Expensify/App/pull/41898/files#diff-a15d3e01be92ab98c02424f703df250303283d66591b3a86aa825534278e0d4cR65, reverting PR solves the empty space issue

Untitled.mov

@ishpaul777
Copy link
Contributor

ishpaul777 commented May 14, 2024

There's another issue i noticed after the revert the expense details report is not in LHN (reproduce on prod. also)

PROD VIDEO:

Screen.Recording.2024-05-14.at.10.27.53.PM.mov

@thienlnam thienlnam added Daily KSv2 and removed DeployBlockerCash This issue or pull request should block deployment Hourly KSv2 labels May 14, 2024
@thienlnam
Copy link
Contributor

Removing the blocker for this reasoning

  1. It only happens if you try to create multiple submits and open one offline, but doesn’t actually prevent you from doing anything
  2. The reduction in memory is a more important PR

That being said, we should aim to fix this soon but not a blocker since it's a specific offline flow

@melvin-bot melvin-bot bot removed the Overdue label May 16, 2024

This comment was marked as outdated.

@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Overdue Daily KSv2 labels May 16, 2024
@mountiny mountiny self-assigned this May 20, 2024
@mountiny
Copy link
Contributor

Jack is ooo, I will take this over

@mountiny mountiny changed the title [$250] Expense - LHN shows blank row when opening transaction thread [UX Reliability] [$250] Expense - LHN shows blank row when opening transaction thread May 20, 2024
@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels May 29, 2024
@melvin-bot melvin-bot bot changed the title [UX Reliability] [$250] Expense - LHN shows blank row when opening transaction thread [HOLD for payment 2024-06-05] [UX Reliability] [$250] Expense - LHN shows blank row when opening transaction thread May 29, 2024
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label May 29, 2024
Copy link

melvin-bot bot commented May 29, 2024

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

Copy link

melvin-bot bot commented May 29, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.76-7 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 2024-06-05. 🎊

For reference, here are some details about the assignees on this issue:

@mountiny mountiny added the Bug Something is broken. Auto assigns a BugZero manager. label May 30, 2024
Copy link

melvin-bot bot commented May 30, 2024

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.

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels May 30, 2024
@mountiny
Copy link
Contributor

I believe this will be $250 to @DylanDylann as the only payment on this issue

@melvin-bot melvin-bot bot added the Overdue label Jun 3, 2024
@twisterdotcom
Copy link
Contributor

Offer sent. Will pay out on Wednesday.

@melvin-bot melvin-bot bot added Daily KSv2 and removed Overdue Daily KSv2 labels Jun 3, 2024
@twisterdotcom
Copy link
Contributor

Payment Summary:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor
Projects
Development

No branches or pull requests

9 participants