Skip to content

[HOLD for payment 2024-08-02] [$125] Dupe detect - Receipt field is not disabled and green thumbnail is shown after adding receipt #45814

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: 9.0.10-2
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:

Break down in numbered steps

Expected Result:

Describe what you think should've happened

Actual Result:

Describe what actually happened

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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

Bug6547677_1721436317991.20240720_084308.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~019db4c5df08390374
  • Upwork Job ID: 1815200683754172578
  • Last Price Increase: 2024-07-22
  • Automatic offers:
    • Krishna2323 | Contributor | 103212255
Issue OwnerCurrent Issue Owner: @jayeshmangwani

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Jul 20, 2024
  2. github-actions commented on Jul 20, 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. melvin-bot commented on Jul 20, 2024

    @melvin-bot

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

  4. lanitochka17 commented on Jul 20, 2024

    @lanitochka17
    Author

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

  5. Krishna2323 commented on Jul 20, 2024

    @Krishna2323
    Contributor

    Proposal

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

    Dupe detect - Receipt field is not disabled and green thumbnail is shown after adding receipt

    What is the root cause of that problem?

    We aren't disabling the empty receipt view when readonly prop is true in MoneyRequestView.

    <ReceiptEmptyState
    hasError={hasErrors}
    disabled={!canEditReceipt}
    onPress={() =>
    Navigation.navigate(
    ROUTES.MONEY_REQUEST_STEP_SCAN.getRoute(
    CONST.IOU.ACTION.EDIT,
    iouType,
    transaction?.transactionID ?? '-1',
    report?.reportID ?? '-1',
    Navigation.getActiveRouteWithoutParams(),
    ),
    )
    }
    />

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

    We should add || readonly to disabled prop of ReceiptEmptyState.

    disabled={!canEditReceipt || readonly}

    What alternative solutions did you explore? (Optional)

    We might also want to disable the receipt view when receipt is present, for that we can update enablePreviewModal prop to enablePreviewModal={!readonly}

    <ReportActionItemImage
    thumbnail={receiptURIs?.thumbnail}
    fileExtension={receiptURIs?.fileExtension}
    isThumbnail={receiptURIs?.isThumbnail}
    image={receiptURIs?.image}
    isLocalFile={receiptURIs?.isLocalFile}
    filename={receiptURIs?.filename}
    transaction={transaction}
    enablePreviewModal

  6. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Jul 21, 2024
  7. mountiny commented on Jul 21, 2024

    @mountiny
    Contributor

    Dupe detection is behind beta so we can remove the blocker

    cc @kubabutkiewicz @pecanoro @parasharrajat

  8. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jul 22, 2024
  9. 22 remaining items

  10. changed the title [-][$125] Dupe detect - Receipt field is not disabled and green thumbnail is shown after adding receipt[/-] [+][HOLD for payment 2024-08-02] [$125] Dupe detect - Receipt field is not disabled and green thumbnail is shown after adding receipt[/+] on Jul 26, 2024
  11. melvin-bot commented on Jul 26, 2024

    @melvin-bot

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

  12. melvin-bot commented on Jul 26, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.12-0 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-08-02. 🎊

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

  13. jayeshmangwani commented on Aug 1, 2024

    @jayeshmangwani
    Contributor
    • [@jayeshmangwani] The PR that introduced the bug has been identified. Link to the PR: Feat/dupe detection confirmation #42571
    • [@jayeshmangwani] 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: Feat/dupe detection confirmation #42571 (comment)
    • [@jayeshmangwani] 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: N/A
    • [@jayeshmangwani] Determine if we should create a regression test for this bug. This feature is behind the beta. I don't think it needs regression testing at the moment.
    • [@jayeshmangwani] 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.
  14. melvin-bot commented on Aug 2, 2024

    @melvin-bot

    Issue is ready for payment but no BZ is assigned. @miljakljajic you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!

  15. miljakljajic commented on Aug 5, 2024

    @miljakljajic
    Contributor

    @jayeshmangwani is owed 125 USD for their work on this issue

    @Krishna2323 was paid in Upwork

  16. jayeshmangwani commented on Aug 5, 2024

    @jayeshmangwani
    Contributor

    Requested as per #45814 (comment)

  17. JmillsExpensify commented on Aug 5, 2024

    @JmillsExpensify
    Contributor

    $125 approved for @jayeshmangwani

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 productionDailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions