Skip to content

[HOLD for payment 2024-01-03] Comment doesn't update to the Merchant name in the split preview component after the receipt scan completes  #29732

Closed

Description

@trjExpensify

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: v1.3.84-4
Reproducible in staging?: Yes
Reproducible in production?:
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: @trjExpensify
Slack conversation: (internal ref) https://expensify.slack.com/archives/C02NZ2HGJAZ/p1697490579346919?thread_ts=1697488517.137999&cid=C02NZ2HGJAZ

Action Performed:

  1. Global create > Request money > scan a receipt
  2. Select 2 participants to split > add a description on the confirmation page > confirm
  3. Wait for receipt scanning to complete
  4. Observe the split preview component in the groupDM contains the comment
  5. Observe the iouReport preview component in each of the DM's between payer:participant contains the merchant

Expected Result:

When the receipt scanning completes, the split preview component should update with the merchant name

Actual Result:

When the receipt scanning completes, the split preview component remains as the description

Workaround:

N/A

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

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari image
MacOS: Desktop

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01c51bbff62b3a32f7
  • Upwork Job ID: 1714065110591516672
  • Last Price Increase: 2023-10-16

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 16, 2023
  2. melvin-bot commented on Oct 16, 2023

    @melvin-bot

    Current assignee @youssef-lr is eligible for the Engineering assigner, not assigning anyone new.

  3. melvin-bot commented on Oct 16, 2023

    @melvin-bot

    Current assignee @trjExpensify is eligible for the Bug assigner, not assigning anyone new.

  4. melvin-bot commented on Oct 16, 2023

    @melvin-bot
  5. melvin-bot commented on Oct 16, 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
  6. melvin-bot commented on Oct 16, 2023

    @melvin-bot

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

  7. trjExpensify commented on Oct 16, 2023

    @trjExpensify
    ContributorAuthor

    👋 @youssef-lr keeping this one internal and assigned to us for the time being. Maybe the work with the empty merchant has caught this one, but logging it so we have it if not.

  8. youssef-lr commented on Oct 19, 2023

    @youssef-lr
    Contributor

    Working on this tomorrow.

  9. 35 remaining items

  10. trjExpensify commented on Jan 3, 2024

    @trjExpensify
    ContributorAuthor

    I think we're good to close this as @robertKozik payment will be handled elsewhere. Regression test for this should be covered in https://github.com/Expensify/Expensify/issues/356417 holistically.

  11. aimane-chnaif commented on Jan 3, 2024

    @aimane-chnaif
    Contributor

    @trjExpensify I was C+ reviewer in PR

  12. trjExpensify commented on Jan 3, 2024

    @trjExpensify
    ContributorAuthor

    Oh! Sorry, I thought that was the other one!

  13. trjExpensify commented on Jan 3, 2024

    @trjExpensify
    ContributorAuthor

    So @aimane-chnaif you're due $500 for the C+ review?

  14. aimane-chnaif commented on Jan 3, 2024

    @aimane-chnaif
    Contributor

    So @aimane-chnaif you're due $500 for the C+ review?

    yes

  15. trjExpensify commented on Jan 3, 2024

    @trjExpensify
    ContributorAuthor

    Cool, offer sent.

  16. trjExpensify commented on Jan 5, 2024

    @trjExpensify
    ContributorAuthor

    Paid!

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.DailyKSv2EngineeringInternalRequires API changes or must be handled by Expensify staff

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions