[HOLD] Chat - Unable to access deleted group member profile

[kbecciv]

HOLD for: https://github.com/Expensify/Expensify/issues/292707 which should fix this.

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

---

Action Performed:

1. Go to staging.new.expensify.com
2. Create a group chat with two users.
3. As one of the two users, close the account.
4. As the user who creates the account, go to chat detail page.
5. Access the deleted group member profile.

Expected Result:

User is able to access the deleted group member profile.

Actual Result:

User is unable to access the deleted group member profile. The profile is hidden.

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.2.29.1

Reproducible in staging?: yes

Reproducible in production?: no

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

Bug6098582_Screen_Recording_20230619_205519_Chrome.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[OSBotify]

👋 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.

[melvin-bot]

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

[luacmartins]

This is expected for now and will be solved in https://github.com/Expensify/Expensify/issues/292707. Context https://expensify.slack.com/archives/C07J32337/p1687190246037479

[tylerkaraszewski]

@luacmartins - should we just close this out in that case?

[luacmartins]

Sure, we can close this.