Skip to content

[$250] IOU - Green dot shows up in LHN briefly when requeting money from another user #39447

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.4.59-0
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
  2. Go to 1:1 DM
  3. Pin the chat
  4. Create an IOU request
  5. Go to IOU report
  6. Create a second request

Expected Result:

Green dot will not show up in LHN when requeting money from another user

Actual Result:

Green dot shows up in LHN briefly when requeting money from another user

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

Bug6435614_1712065747860.20240402_214557.mp4
Bug6435614_1712065828320.20240402_214912.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~017992a05a461e2089
  • Upwork Job ID: 1775313856042840064
  • Last Price Increase: 2024-04-03

Activity

  1. melvin-bot commented on Apr 2, 2024

    @melvin-bot

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

  2. github-actions commented on Apr 2, 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.
  3. lanitochka17 commented on Apr 2, 2024

    @lanitochka17
    Author

    @roryabraham 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

  4. lanitochka17 commented on Apr 2, 2024

    @lanitochka17
    Author

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

  5. roryabraham commented on Apr 2, 2024

    @roryabraham
    Contributor

    reproduced locally on main

  6. roryabraham commented on Apr 2, 2024

    @roryabraham
    Contributor

    reproduced locally on the production branch as well

  7. roryabraham commented on Apr 3, 2024

    @roryabraham
    Contributor

    reproduced in production, demoting

  8. added
    ExternalAdded to denote the issue can be worked on by a contributor
    and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Apr 3, 2024
  9. 29 remaining items

  10. nkdengineer commented on Apr 4, 2024

    @nkdengineer
    Contributor

    thanks again for pointing out that issue @nkdengineer - the reproduction steps were very helpful. I ended up fixing the problem in a different way.

    @roryabraham There're other regressions with that approach too, please note needsToBeManuallySubmitted is also used here and here

    I'm quite certain that needsToBeManuallySubmitted should only be true for expense reports.

    @roryabraham I think the problem here is that the naming of needsToBeManuallySubmitted is confusing.

    The use case for that method is:
    If this report is an expense report, and it has automatic submit, then hasOutstandingChildRequest will always be false (it's the intention of this condition)

    That's why needsToBeManuallySubmitted returns true for personal request, so that the hasOutstandingChildRequest will not be forced to be false here, but will depend on other conditions.

    We should instead rename to hasAutomaticSubmission (which is an inverted version of needsToBeManuallySubmitted)

    And we'll use hasAutomaticSubmission(iouReport) here

    And use !hasAutomaticSubmission here and here

  11. nkdengineer commented on Apr 4, 2024

    @nkdengineer
    Contributor

    I'm still not sure about your RCA though

    @roryabraham Did you try keeping the some logic we had to make admins see expense reports that will be automatically submitted with a green dot (mentioned here)? You'll see the bug in the OP is not fixed right? That's because the RCA is there as I mentioned in my proposal

    And the needsToBeManuallySubmitted fix doesn't fix the root cause but it's more like a code polish.

  12. roryabraham commented on Apr 10, 2024

    @roryabraham
    Contributor

    There're other regressions with that approach too

    Can you please provide reproduction steps for these other regressions?

  13. melvin-bot commented on May 7, 2024

    @melvin-bot

    This issue has not been updated in over 15 days. @twisterdotcom, @abdulrahuman5196, @roryabraham eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  14. twisterdotcom commented on May 13, 2024

    @twisterdotcom
    Contributor

    Are we still waiting on a response to @roryabraham from @nkdengineer here?

  15. abdulrahuman5196 commented on May 22, 2024

    @abdulrahuman5196
    Contributor

    Are we still waiting on a response to @roryabraham from @nkdengineer here?

    Yes.

  16. melvin-bot commented on Jul 19, 2024

    @melvin-bot

    @twisterdotcom, @abdulrahuman5196, @roryabraham, this Monthly task hasn't been acted upon in 6 weeks; closing.

    If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

  17. mvtglobally commented on Jul 22, 2024

    @mvtglobally

    Issue is not reproducible

    Recording.2174.mp4
  18. roryabraham commented on Jul 22, 2024

    @roryabraham
    Contributor

    That adds up. When I went back to my draft PR, merging main it looked like the core changes had already been made somewhere else. Closing this out

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringExternalAdded to denote the issue can be worked on by a contributorMonthlyKSv2Not a priorityReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions