Individual IOUs from bill split are not correctly sent to other devices

[m-natarajan]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 1.4.66-2 Reproducible in staging?: needs reproduction Reproducible in production?: needs reproduction If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): @roryabraham @thienlnam Logs: https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by: @thienlnam Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1714154876284589

Action Performed:

1. Log into New Expensify on two devices, A and B.
2. Create a group on device A.
3. Upload a receipt to split a bill in the group.

Expected Result:

On both devices, individual IOUs should be created with each member of the group for their portion.

Actual Result:

Individual IOUs appear on the device where the receipt was uploaded. They do not appear on device B.

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• [ ] Android: Native
• [ ] Android: mWeb Chrome
• [x] iOS: Native
• [ ] iOS: mWeb Safari
• [x] MacOS: Chrome / Safari
• [ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

[melvin-bot[bot]]

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot[bot]]

Job added to Upwork: https://www.upwork.com/jobs/~0128f10261fc2f1ffb

[melvin-bot[bot]]

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

[johncschuster]

This was just triaged. Not overdue

[johncschuster]

@mananjadhav what do you need from me on this one?

[mananjadhav]

Waiting on proposals. I'll also try to reproduce it at my end

[johncschuster]

Oh! It looks like this is an Internal issue so it's likely not going to be seen in the usual Help Wanted spaces. How can I help drum up proposals?

[melvin-bot[bot]]

@mananjadhav @johncschuster this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[melvin-bot[bot]]

@mananjadhav, @johncschuster Whoops! This issue is 2 days overdue. Let's get this updated quick!

[johncschuster]

Ok, I'm unsure the priority of this issue in the grander scheme (and thus, how aggressive I should be to get a volunteer). Raising the question here

[johncschuster]

Ok! We chatted about the priority of this issue. Currently, this is a MEDIUM priority. It's important we get someone on this, but it's not the most urgent thing.

[johncschuster]

Setting this to Weekly in the meantime.

[mananjadhav]

Still waiting for this to get picked up.

[johncschuster]

I couldn't action this today. I will pop back in tomorrow

[mananjadhav]

Should we make this monthly @johncschuster ?

[johncschuster]

@arielgreen, we haven't gotten any traction on this one. Do you feel we need to keep this at Weekly and pump the gas, or do you feel we can safely reduce the priority to Monthly for now?

[johncschuster]

Reducing to Monthly. Please change the label if you disagree!

[johncschuster]

Asking for help to get some engineering resources on this one.

[mvtglobally]

Issue not reproducible during KI retests. (First week)

[johncschuster]

It sounds like this may not be reproducible. Closing!