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

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

About this issue

  • Original URL
  • State: closed
  • Created 8 months ago
  • Comments: 29 (14 by maintainers)

Most upvoted comments

⚠️ 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.