Skip to content

[HOLD for payment 2022-11-16] [$250] Chat - App is crashed after click on expensifail account which is closed #12487

Closed

Description

@kbecciv

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:

Precondition:
Create a group conversation with account A and B ( should be expensifail account)
Close the expensifail account under domain account

  1. Go to staging.new.expensify.com
  2. Log in with account A
  3. Select the created conversation between account A and B from LHN
  4. Click on user's B avatar

Expected Result:

Details for account B should be displayed.

Actual Result:

App is crashed after click on expensifail account which is closed

Workaround:

Unknown

Platform:

Where is this issue occurring?

  • Web
  • iOS
  • Android
  • Desktop App
  • Mobile Web

Version Number: 1.2.24.0

Reproducible in staging?: Yes

Reproducible in production?: No

Email or phone of affected tester (no customers): 508-221-1196/applausetester+0709abb@applause.expensifail.com

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Recording.1619.mp4

image (29)

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Activity

  1. OSBotify commented on Nov 4, 2022

    @OSBotify
    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.
  2. melvin-bot commented on Nov 4, 2022

    @melvin-bot

    Triggered auto assignment to @marcaaron (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  3. kbecciv commented on Nov 4, 2022

    @kbecciv
    Author

    Issue is not reproducible in production
    image (30)

  4. marcaaron commented on Nov 5, 2022

    @marcaaron
    Contributor

    Go to staging.new.expensify.com
    Log in with account A
    Select the created conversation between account A and B from LHN
    Click on account B

    Not able to reproduce this. Please list the exact testing steps that were performed in order to trigger the bug.

  5. kbecciv commented on Nov 5, 2022

    @kbecciv
    Author
    1. Go to staging.new.expensify.com
    2. Log in with account A (50821-11-96/Feya86Katya
    3. Select the chat conversation with applausetester+0709abb@applause.expensifail.com
    4. Click on applausetester+0709abb@applause.expensifail.com avatar
  6. 0xmiroslav commented on Nov 5, 2022

    @0xmiroslav
    Contributor

    Proposal

    displayName: ReportUtils.getDisplayNameForParticipant({login}),

    Root cause:
    This line was added here - #12364
    and regressed by #12399

    Solution:

    -               displayName: ReportUtils.getDisplayNameForParticipant({login}),
    +               displayName: ReportUtils.getDisplayNameForParticipant(login),
  7. 0xmiroslav commented on Nov 5, 2022

    @0xmiroslav
    Contributor
  8. melvin-bot commented on Nov 6, 2022

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  9. tgolen commented on Nov 7, 2022

    @tgolen
    Contributor

    Ah yes, it looks like when I changed the signature of getDisplayNameForParticipant() that I missed a spot. The proposal from @0xmiroslav looks like a good fix for it.

  10. 46 remaining items

  11. joekaufmanexpensify commented on Nov 16, 2022

    @joekaufmanexpensify
    Contributor

    Discussing two new regression tests I think we should add here.

  12. joekaufmanexpensify commented on Nov 17, 2022

    @joekaufmanexpensify
    Contributor

    Regression test sent to applause to be added! Linked in BZ checklist above.

  13. joekaufmanexpensify commented on Nov 17, 2022

    @joekaufmanexpensify
    Contributor

    Okay, I updated the bug zero checklist above to reflect who is responsible for which tasks (as the checklist itself was just updated, before after it was posted to this issue).

    @marcaaron / @parasharrajat let me know if I can help with commenting on the offending PR and beginning the discussion in Slack.

    In the interim, I am going to pay everyone.

  14. joekaufmanexpensify commented on Nov 17, 2022

    @joekaufmanexpensify
    Contributor

    @parasharrajat Mind accepting the offer for this one so we can pay you?

  15. marcaaron commented on Nov 17, 2022

    @marcaaron
    Contributor
  16. marcaaron commented on Nov 17, 2022

    @marcaaron
    Contributor
  17. parasharrajat commented on Nov 17, 2022

    @parasharrajat
    Member
  18. joekaufmanexpensify commented on Nov 18, 2022

    @joekaufmanexpensify
    Contributor

    Great ty! Since this PR was merge the same day the contributor was assigned to the issue, both @parasharrajat and @0xmiroslav get a 50% bonus.

    Going to issue payment of $375 to both of you now!

  19. joekaufmanexpensify commented on Nov 18, 2022

    @joekaufmanexpensify
    Contributor

    @parasharrajat $375 sent!

  20. joekaufmanexpensify commented on Nov 18, 2022

    @joekaufmanexpensify
    Contributor

    @0xmiroslav $375 sent!

  21. joekaufmanexpensify commented on Nov 18, 2022

    @joekaufmanexpensify
    Contributor

    Applause found this, so no reporting payment to make.

  22. joekaufmanexpensify commented on Nov 18, 2022

    @joekaufmanexpensify
    Contributor

    Job closed.

  23. joekaufmanexpensify commented on Nov 18, 2022

    @joekaufmanexpensify
    Contributor

    This is all set. Confirming whether the issue needs to remain open until applause adds regression test.

  24. joekaufmanexpensify commented on Nov 18, 2022

    @joekaufmanexpensify
    Contributor

    Okay, confirmed we don't need to wait for applause to actually add the regression test. Opening the issue for them is sufficient.

    Closing as this is all set. Thanks everyone!

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions