Skip to content

[$250] Group chat - Blank name in "This chat is with " when creating group chat with yourself #50390

Closed

Description

@IuliiaHerets

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: 9.0.46-1
Reproducible in staging?: Y
Reproducible in production?: N/A - new feature, doesn't exist in prod
Email or phone of affected tester (no customers): applausetester+pso@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to FAB > Start chat.
  3. Click Add to group next to any user.
  4. Click Next.
  5. Unselect the user on the confirmation page.
  6. Click Start group.

Expected Result:

The copy at the beginning of the conversation should include the current user.

Actual Result:

The copy at the beginning of the conversation is "This chat is with " which shows blank name.

Workaround:

Unknown

Platforms:

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6628148_1728379695818.20241008_172523.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021843674144504172090
  • Upwork Job ID: 1843674144504172090
  • Last Price Increase: 2024-10-08
Issue OwnerCurrent Issue Owner: @parasharrajat

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 8, 2024
  2. melvin-bot commented on Oct 8, 2024

    @melvin-bot

    Triggered auto assignment to @madmax330 (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  3. melvin-bot commented on Oct 8, 2024

    @melvin-bot

    Triggered auto assignment to @lschurr (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.

  4. github-actions commented on Oct 8, 2024

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  5. Nodebrute commented on Oct 8, 2024

    @Nodebrute
    Contributor

    Edited by proposal-police: This proposal was edited at 2024-10-08 10:29:59 UTC.

    Proposal

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

    Blank name in "This chat is with " when creating group chat with yourself

    What is the root cause of that problem?

    From here we get the participant accountID and we pass true for shouldForceExcludeCurrentUser

    const participantAccountIDs = ReportUtils.getParticipantsAccountIDsForDisplay(report, undefined, undefined, true);

    and in here we use shouldExcludeCurrentUser which will be true cause we are passing true for shouldForceExcludeCurrentUser
    const shouldExcludeCurrentUser = isOneOnOneChat(report) || isSystemChat(report) || shouldForceExcludeCurrentUser;

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

    We can use isGroupchat check here

        const isGroupChat = ReportUtils.isGroupChat(report)
    

    If isGroupChat is true we can pass false for shouldForceExcludeCurrentUser.

    What alternative solutions did you explore? (Optional)

    Alternative solution would be not to add any check

    const participantAccountIDs = ReportUtils.getParticipantsAccountIDsForDisplay(report, undefined, undefined, true);

        const participantAccountIDs = ReportUtils.getParticipantsAccountIDsForDisplay(report, undefined, undefined);
    

    Alternative 2
    Or we could simply add !isGroupChat here

          const shouldExcludeCurrentUser = isOneOnOneChat(report) || isSystemChat(report) || (shouldForceExcludeCurrentUser && !isGroupChat(report));
    
  6. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Oct 8, 2024
  7. changed the title [-]Group chat - Blank name in "This chat is with " when creating group chat with yourself[/-] [+][$250] Group chat - Blank name in "This chat is with " when creating group chat with yourself[/+] on Oct 8, 2024
  8. melvin-bot commented on Oct 8, 2024

    @melvin-bot
  9. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Oct 8, 2024
  10. melvin-bot commented on Oct 8, 2024

    @melvin-bot

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

  11. parasharrajat commented on Oct 8, 2024

    @parasharrajat
    Member

    Why would a user create a group chat with himself? Is this expected @lschurr @madmax330 ?

    Shouldn't we prevent this from happening?

    https://expensify.slack.com/archives/C01GTK53T8Q/p1728401433760799

  12. parasharrajat commented on Oct 8, 2024

    @parasharrajat
    Member

    OK so this is expected behaviour as per #39317 (comment).

  13. Nodebrute commented on Oct 8, 2024

    @Nodebrute
    Contributor

    @parasharrajat Are we considering this issue as a regression from #47427?

  14. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Oct 8, 2024
  15. thienlnam commented on Oct 8, 2024

    @thienlnam
    Contributor

    Doesn't look like it needs to be a blocker

  16. parasharrajat commented on Oct 8, 2024

    @parasharrajat
    Member

    @Nodebrute Yes. It is a regression from #47427

  17. parasharrajat commented on Oct 9, 2024

    @parasharrajat
    Member

    @nkdengineer is fixing this issue. we can remove help wanted label.

  18. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Oct 9, 2024
  19. parasharrajat commented on Oct 10, 2024

    @parasharrajat
    Member

    PR merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions