Skip to content

IOU - Money Request and Split bill missing from LNH #22924

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!


Action Performed:

Preconditions:
Must be logged in with the account workprofiletestuser@gmail.com
Steps:

  1. Open https://staging.new.expensify.com/
  2. Click on the "Global action" button (Big green plus button in LHN)
  3. Click on "Request money"
  4. In the right column, enter any amount
  5. Click on the "Next" button
  6. In the search bar, type workprofiletestuser+5@gmail.com
  7. Click the "Request {Currency}{Quantity}" button
  8. Click on the user name with the red circle in the LHN from step 6

Expected Result:

When a user commits an IOU and sends another user request money, split bill, then an IOU should appear in LNH with that user

Actual Result:

When a user commits an IOU and sends another user request money, split bill, the IOU appears grayed out in LNH and when clicked it disappears

Workaround:

Unknown

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.3.41.1

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

Bug6128548_Recording__28.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

Activity

  1. OSBotify commented on Jul 14, 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.
  2. melvin-bot commented on Jul 14, 2023

    @melvin-bot

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

  3. cead22 commented on Jul 17, 2023

    @cead22
    Contributor

    Following the steps here worked for me. It looks like this request may have failed for @lanitochka17, I'm gonna see if I can find logs
    image

  4. mountiny commented on Jul 17, 2023

    @mountiny
    Contributor

    Looking at the logs we get 406 Chat report with these participants already exists with different ID

    Hence I believe this is the same instance of #22663 where the issue is stemming from the fact the other user is not knownUser and hence we dont retrieve the login field for them, which is needed to find the correct chat/ or pass the correct email to the command.

    I dont think this should be a deploy blocker but its something we have to resolve after the secure login migration as there is no clear plan ahead afaik. Alex B is ooo today and Puneet is out for a week so we should probs discuss tomorrow

  5. cead22 commented on Jul 17, 2023

    @cead22
    Contributor

    Preconditions:
    Must be logged in with the account workprofiletestuser@gmail.com

    I missed this, but now I'm able to reproduce, and I think I found a relevant error in the logs

    Throwing exception with message: '406 Chat report with these participants already exists with different ID' from auth/lib/Transaction.cpp:1638
    Error processing command 'CreateIOUTransaction' (406 Chat report with these participants already exists with different ID), ignoring.

  6. cead22 commented on Jul 17, 2023

    @cead22
    Contributor

    I reproduced the error in production (logs), so I don't think we need to block on this, since it also fails, even though it looks a little different

  7. added
    ImprovementItem broken or needs improvement.
    and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Jul 17, 2023
  8. cead22 commented on Jul 17, 2023

    @cead22
    Contributor

    Closing since this is kind of a duplicate of #16105 (comment) and #22663 and it should be fixed by the same fix that addresses those

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions