Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.36k stars 2.78k forks source link

[$500] IOU - Split bill in room of participant is shown empty in mweb& loading in android #26956

Closed lanitochka17 closed 1 year ago

lanitochka17 commented 1 year ago

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Launch app
  2. Tap Profile
  3. Tap Workspaces
  4. Select a workspace
  5. Tap on top right 3 dot
  6. Tap announce room
  7. Tap plus icon near compose
  8. Tap Split bill
  9. Tap enter amount
  10. Tap next
  11. Tap split money
  12. Open a split money participant account (mweb)
  13. From LHN, Open announce room split bill to note split bill transaction is empty

Or Pre-condition: a room created

  1. Go to https://staging.new.expensify.com/
  2. Open a room created
  3. Repeat steps 7 - step 11
  4. Open a split money participant account(android)
  5. From LHN, Open announce room split bill to note split bill transaction

Expected Result:

The split bill transaction in room of participant must be shown correctly with amount and participants details in both mweb and android. It should not be empty(mweb) and keeps loading as in android

Actual Result:

He split bill transaction in room of participant is shown empty in mweb and keeps loading in android

Workaround:

Unknown

Platforms:

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

Version Number: 1.3.65-0

Reproducible in staging?: Yes

Reproducible in production?: Yes

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

Notes/Photos/Videos: Any additional supporting documentation

https://github.com/Expensify/App/assets/78819774/b363b0fd-ddaf-4d00-aa8d-d3db64b77cd0

https://github.com/Expensify/App/assets/78819774/34727adc-48e0-424a-86f4-8988bb59f0c1

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~013eb2d17255ea6583
  • Upwork Job ID: 1699828711453896704
  • Last Price Increase: 2023-09-07
melvin-bot[bot] commented 1 year ago

Triggered auto assignment to @isabelastisser (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

melvin-bot[bot] commented 1 year ago

Bug0 Triage Checklist (Main S/O)

melvin-bot[bot] commented 1 year ago

Job added to Upwork: https://www.upwork.com/jobs/~013eb2d17255ea6583

melvin-bot[bot] commented 1 year ago

Current assignee @isabelastisser is eligible for the External assigner, not assigning anyone new.

melvin-bot[bot] commented 1 year ago

Triggered auto assignment to Contributor-plus team member for initial proposal review - @situchan (External)

ayazalavi commented 1 year ago

@lanitochka17 @situchan is it reproducible over the desktop mac? Can you share video for that?

tienifr commented 1 year ago

I tried reproducing this one and found the Pusher did not return the transaction, only the report action. That's why it keeps loading. Should be handled internally.

ayazalavi commented 1 year ago

@tienifr anything i can do in this ticket?

melvin-bot[bot] commented 1 year ago

Current assignee @situchan is eligible for the Internal assigner, not assigning anyone new.

melvin-bot[bot] commented 1 year ago

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

melvin-bot[bot] commented 1 year ago

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

isabelastisser commented 1 year ago

Hey @situchan how can we move this forward?

isabelastisser commented 1 year ago

@situchan, can you see my comment above? Should an Expensify engineer handle this? Can you reproduce this?

melvin-bot[bot] commented 1 year ago

@isabelastisser, @situchan Eep! 4 days overdue now. Issues have feelings too...

situchan commented 1 year ago

I agree to handle this internally

isabelastisser commented 1 year ago

Hey @situchan, can this still be reproduced?

melvin-bot[bot] commented 1 year ago

@isabelastisser @situchan 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!

situchan commented 1 year ago

I am not able to reproduce. @lanitochka17 can you please test on latest version?

isabelastisser commented 1 year ago

Closing as this can not be reproduced.