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

CRITICAL: [Actionable Whispers] Track scan expense is duplicated when it is submitted to someone #40485

Closed
6 tasks done
lanitochka17 opened this issue Apr 18, 2024 · 10 comments
Closed
6 tasks done
Assignees
Labels
Daily KSv2 Engineering Internal Requires API changes or must be handled by Expensify staff

Comments

@lanitochka17
Copy link

lanitochka17 commented Apr 18, 2024

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!


Version Number: 1.4.63-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

Issue found when executing PR #38709

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to FAB > Track expense
  3. Create a track scan expense
  4. From the whisper, select Submit it to someone
  5. Select a user to submit to
  6. In 1:1 DM with the user from Step 5, click on the expense preview
  7. Click on the header subtitle to return to main chat
  8. Click on the same chat in LHN

Expected Result:

he track scan expense will not be duplicated

Actual Result:

The track scan expense is duplicated when it is submitted to someone

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

Bug6453775_1713454164236.bandicam_2024-04-18_23-24-56-667.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01a279eb4ea7ee1906
  • Upwork Job ID: 1781106389210488832
  • Last Price Increase: 2024-04-18
@lanitochka17 lanitochka17 added the DeployBlockerCash This issue or pull request should block deployment label Apr 18, 2024
Copy link

melvin-bot bot commented Apr 18, 2024

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

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.

@lanitochka17
Copy link
Author

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

@cead22 cead22 assigned thienlnam and unassigned cead22 Apr 18, 2024
@thienlnam thienlnam moved this to CRITICAL in [#whatsnext] #vip-vsb Apr 18, 2024
@thienlnam thienlnam added Daily KSv2 and removed DeployBlockerCash This issue or pull request should block deployment Hourly KSv2 labels Apr 18, 2024
@thienlnam
Copy link
Contributor

Doesn't look like it needs to be a blocker, but it looks like the main issue is that we're not using the passed reportActionID in the BE for the moneyRequestPreviewAction

@thienlnam thienlnam added the Internal Requires API changes or must be handled by Expensify staff label Apr 18, 2024
Copy link

melvin-bot bot commented Apr 18, 2024

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

Copy link

melvin-bot bot commented Apr 18, 2024

Triggered auto assignment to Contributor Plus for review of internal employee PR - @thesahindia (Internal)

@quinthar quinthar changed the title Track expense - Track scan expense is duplicated when it is submitted to someone CRITICAL: [Actionable Whispers] Track scan expense is duplicated when it is submitted to someone Apr 19, 2024
@dangrous
Copy link
Contributor

Notes from DM with @thienlnam

Inside the money request report, there should be IOU reportActions (which we've renamed to MoneyRequestPreviews).

And then when you click on that, you are taken to the money request reportIn the DM, there should be a REPORTPREVIEW reportAction added or updated

But basically I think what needs to happen is we need to start accepting a new parameter in the BE called report reportPreviewReportActionID, and ensure that we use that reportID for the REPORTPREVIEW reportAction

@quinthar
Copy link
Contributor

What's the next step here -- is @thienlnam taking this, or @dangrous ?

@melvin-bot melvin-bot bot added the Overdue label Apr 21, 2024
@thienlnam
Copy link
Contributor

I'm still taking this since @dangrous will be out this week

@melvin-bot melvin-bot bot added Overdue and removed Overdue labels Apr 22, 2024
@thienlnam
Copy link
Contributor

Done! Changes are live

@melvin-bot melvin-bot bot removed the Overdue label Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Daily KSv2 Engineering Internal Requires API changes or must be handled by Expensify staff
Projects
No open projects
Status: CRITICAL
Development

No branches or pull requests

6 participants