Skip to content

[HOLD for payment 2024-01-11] [$500] IOU- When replacing receipt and downloading it, previous receipt with new receipt name is downloaded #33363

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!


Version Number: 1.4.14-2
Reproducible in staging?: Y
Reproducible in production?: Y
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
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

  1. Navigate to IOU request details that has a receipt
  2. Click on the receipt
  3. Click 3-dot menu > Replace
  4. Upload another receipt
  5. After the upload is complete, download the receipt

Expected Result:

The latest receipt will be downloaded

Actual Result:

The previous receipt is downloaded, while the receipt file name is the name of the latest receipt
On Android and iOS app, it downloads the previous receipt (file name is not affected/not relevant) after replacing the receipt

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

Bug6321355_1703082153236.bandicam_2023-12-20_22-14-39-707.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0113378cba031fc595
  • Upwork Job ID: 1737485735446364160
  • Last Price Increase: 2023-12-20
  • Automatic offers:
    • shubham1206agra | Contributor | 28077368
Issue OwnerCurrent Issue Owner: @abdulrahuman5196

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 20, 2023
  2. melvin-bot commented on Dec 20, 2023

    @melvin-bot
  3. changed the title [-]IOU- When replacing receipt and downloading it, previous receipt with new receipt name is downloaded[/-] [+][$500] IOU- When replacing receipt and downloading it, previous receipt with new receipt name is downloaded[/+] on Dec 20, 2023
  4. melvin-bot commented on Dec 20, 2023

    @melvin-bot

    Triggered auto assignment to @alexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  5. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Dec 20, 2023
  6. melvin-bot commented on Dec 20, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  7. melvin-bot commented on Dec 20, 2023

    @melvin-bot

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

  8. namhihi237 commented on Dec 20, 2023

    @namhihi237
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    The link source download does not update when replace the image

    What is the root cause of that problem?

    Currently, when the source changes we don't update in the threeDotsMenuItems.

    What changes do you think we should make in order to solve the problem?

    We should add the source into dependence

    What alternative solutions did you explore? (Optional)

  9. vikssevishnu commented on Dec 20, 2023

    @vikssevishnu

    I am trying to access the issue details using the link "https://stackoverflow.com/c/expensify/questions/14418" but i am getting you do not have access. Can you help on it ?

  10. melvin-bot commented on Dec 20, 2023

    @melvin-bot

    📣 @vikssevishnu! 📣
    Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
    Please follow these steps:

    1. Make sure you've read and understood the contributing guidelines.
    2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
    3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
    4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
      Screen Shot 2022-11-16 at 4 42 54 PM
      Format:
    Contributor details
    Your Expensify account email: <REPLACE EMAIL HERE>
    Upwork Profile Link: <REPLACE LINK HERE>
    
  11. vikssevishnu commented on Dec 20, 2023

    @vikssevishnu

    Contributor details
    Your Expensify account email: vishnu.vikas19@gmail.com
    Upwork Profile Link: https://www.upwork.com/freelancers/~01a59961216a1ee633?viewMode=1

  12. 21 remaining items

  13. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jan 4, 2024
  14. changed the title [-][$500] IOU- When replacing receipt and downloading it, previous receipt with new receipt name is downloaded[/-] [+][HOLD for payment 2024-01-11] [$500] IOU- When replacing receipt and downloading it, previous receipt with new receipt name is downloaded[/+] on Jan 4, 2024
  15. melvin-bot commented on Jan 4, 2024

    @melvin-bot

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

  16. melvin-bot commented on Jan 4, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.21-4 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-01-11. 🎊

    After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

    • External issue reporter
    • Contributor that fixed the issue
    • Contributor+ that helped on the issue and/or PR

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

  17. melvin-bot commented on Jan 4, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@shubham1206agra] The PR that introduced the bug has been identified. Link to the PR:
    • [@shubham1206agra] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    • [@shubham1206agra] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
    • [@shubham1206agra] Determine if we should create a regression test for this bug.
    • [@shubham1206agra] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@alexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  18. melvin-bot commented on Jan 5, 2024

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  19. alexpensify commented on Jan 9, 2024

    @alexpensify
    Contributor

    @shubham1206agra - can you please identify if this PR triggered the deploy blocker or if there is another reason for this automation? Thanks!

  20. shubham1206agra commented on Jan 9, 2024

    @shubham1206agra
    Contributor

    Oh it's a false alert actually

  21. alexpensify commented on Jan 9, 2024

    @alexpensify
    Contributor

    @shubham1206agra - can you please share more context as to why the alert is wrong? It will be helpful to have it recorded here. Thanks!

  22. shubham1206agra commented on Jan 9, 2024

    @shubham1206agra
    Contributor

    @alexpensify #33586 is the offending PR. Some contributor marked this by mistake as this issue is already deployed to production.

  23. alexpensify commented on Jan 9, 2024

    @alexpensify
    Contributor

    Thank you! I will continue the process to prepare for the payment date.

  24. alexpensify commented on Jan 11, 2024

    @alexpensify
    Contributor

    Based on the 👎🏼 here #33363 (comment) and the note here #33363 (comment), there is no payment action here since this issue was handled in other GH. I confirmed the Upwork job is closed too.

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions