Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split bill - App crashed when try to split bill via group #22975

Closed
4 of 6 tasks
lanitochka17 opened this issue Jul 16, 2023 · 5 comments
Closed
4 of 6 tasks

Split bill - App crashed when try to split bill via group #22975

lanitochka17 opened this issue Jul 16, 2023 · 5 comments
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2

Comments

@lanitochka17
Copy link

lanitochka17 commented Jul 16, 2023

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


Issue found when executing PR #22643

Action Performed:

  1. Create a brand new account that isn't on a domain with a subscription (xyz@expensify
    ❌ // xyz@gmail.com
    ✅ )
  2. Create a group chat with multiple participants
  3. 'Split Bill' for group

Expected Result:

You should be able to split a bill from someone successfully

Actual Result:

App crashed on iOS. Android App, Button "Split" not active for Mac/Chrome, Desktop App, mweb

Workaround:

Unknown

Platforms:

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

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.3.41.2

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

Bug6130076_22643_Desktop.mp4
Bug6130076_22643_ios.mp4
Bug6130076_22643_Android.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

@lanitochka17 lanitochka17 added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Jul 16, 2023
@melvin-bot
Copy link

melvin-bot bot commented Jul 16, 2023

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

@melvin-bot
Copy link

melvin-bot bot commented Jul 16, 2023

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

@bernhardoj
Copy link
Contributor

Dupe of #21268

@s-alves10
Copy link
Contributor

Proposal

Please re-state the problem that we are trying to solve in this issue.

App crashes when try to split bill with new users

What is the root cause of that problem?

The backend returns personalDetail info with login = 'undefined' for new users as I mentioned #22588 (comment).
So the parameters of Localize.arrayToString includes undefined for newly created accounts.

const formattedParticipants = Localize.arrayToString([currentUserLogin, ..._.map(participants, (participant) => participant.login)]);

This is the root cause

What changes do you think we should make in order to solve the problem?

login field for new users are undefined. Instead they have alternateText(email) and text(display name) fields. We can use this

    const formattedParticipants = Localize.arrayToString([currentUserLogin, ..._.map(participants, (participant) => participant.login || participant.alternateText)]);

This works as expected.

What alternative solutions did you explore? (Optional)

This can be fixed in the backend

@johncschuster
Copy link
Contributor

Closing since this is a duplicate of #21268. Please take all proposals to that issue instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2
Projects
None yet
Development

No branches or pull requests

4 participants