Skip to content

[HOLD for payment 2024-03-14] [HOLD for payment 2024-03-13] [$500] IOU - On scan split with 2 users, individual IOU details page shows hhm not here #37758

@lanitochka17

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.47
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/4382182
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. Launch app
  2. Tap fab-- request money---scan
  3. Upload image using camera
  4. Select 2 contacts as split
  5. Complete the flow & tap split
  6. Open the newly created expense
  7. Enter an amount
  8. Tap split
  9. Open the newly created expense
  10. In details page, tap individual split amount
  11. Tap message user
  12. Tap individual IOU to open details page

Expected Result:

On scan split with 2 users, individual IOU details page must show IOU details

Actual Result:

On scan split with 2 users, individual IOU details
page shows hhm not here

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

Bug6402828_1709645645822.fab.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~014b9c1a7230c9adfe
  • Upwork Job ID: 1765081849283305472
  • Last Price Increase: 2024-03-05

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionEngineeringExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions