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

Track - App shows old receipt when submitting expense with receipt and changing receipt #45062

Closed
6 tasks done
lanitochka17 opened this issue Jul 9, 2024 · 8 comments · Fixed by #45081
Closed
6 tasks done
Assignees
Labels
Engineering Reviewing Has a PR in review Weekly KSv2

Comments

@lanitochka17
Copy link

lanitochka17 commented Jul 9, 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: 9.0.5-5
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4703969
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to self DM
  3. Go to + > Track expense > Manual
  4. Track a manual expense with receipt
  5. Click Submit to someone from the actionable whisper
  6. Select a user and proceed to confirmation page
  7. On confirmation page, click 3-dot menu > Add receipt
  8. Upload a different receipt and submit to the person
  9. Click on the transaction thread

Expected Result:

The receipt view will show the latest uploaded receipt

Actual Result:

The receipt view shows the original uploaded receipt (Step 4) instead of the latest one (Step 8)

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

Bug6536738_1720521133434.bandicam_2024-07-09_18-26-11-551.mp4

View all open jobs on GitHub

@lanitochka17 lanitochka17 added DeployBlockerCash This issue or pull request should block deployment DeployBlocker Indicates it should block deploying the API labels Jul 9, 2024
Copy link

melvin-bot bot commented Jul 9, 2024

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

Copy link
Contributor

github-actions bot commented Jul 9, 2024

👋 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

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

@lanitochka17
Copy link
Author

We think that this bug might be related to #vip-vsp

@rlinoz
Copy link
Contributor

rlinoz commented Jul 9, 2024

Can't repro in v9.0.5-7, closing

Screen.Recording.2024-07-09.at.09.57.31.mov

@rlinoz rlinoz closed this as completed Jul 9, 2024
@lanitochka17
Copy link
Author

Hello @rlinoz This issue is still reproducible again.

You should do a manual expense with receipt, not scan request

Updated steps:

  1. Go to staging.new.expensify.com
  2. Go to self DM
  3. Go to + > Track expense > Manual
  4. Track a manual expense with receipt
  5. Click Submit to someone from the actionable whisper
  6. Select a user and proceed to confirmation page
  7. On confirmation page, click 3-dot menu > Add receipt
  8. Upload a different receipt and submit to the person
  9. Click on the transaction thread

Thank you

@lanitochka17 lanitochka17 reopened this Jul 9, 2024
@rlinoz
Copy link
Contributor

rlinoz commented Jul 9, 2024

Oh this happens because ConvertTrackedExpenseToRequest doesn't accept a receipt, we will just use the one we already have attached to that expense. Let me check if we should change the BE or remove the three dot in this flow.

@rlinoz
Copy link
Contributor

rlinoz commented Jul 9, 2024

We added the threedots here #44670

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Engineering Reviewing Has a PR in review Weekly KSv2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants