[HOLD for payment ASAP] Chat - Unable to initiate chat for a user that doesn't have any messages

[kavimuru]

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. Open app and login
2. Click on + > New Chat
3. Choose a user that doesn't have any messages

Expected Result:

Able to initiate chat with that user

Actual Result:

User is redirected back to Concierge conversation. and error message "The chat you are looking for cannot be found"

Workaround:

Unknown

Platform:

Where is this issue occurring?

• iOS

Version Number: 1.1.18.0

Reproducible in staging?: yes

Reproducible in production?: No

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

Notes/Photos/Videos:

20211206_223806.mp4

Expensify/Expensify Issue URL:

Issue reported by: @thesahindia
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1638604309227900

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.

[MelvinBot]

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

[thesahindia]

Hi @kavimuru , can you please check if this is the same issue that i reported in this
slack thread

[isagoico]

Updated the issue to reflect that it was originally raised by @thesahindia, I missed his thread in the Contributor channel yesterday when I was going through the BUG: messages.

[parasharrajat]

@isagoico Could you please retest it? I believe this is fixed on staging.

[isagoico]

@parasharrajat Issue is still reproducible in the iOS app. All other environments are working as expected.

Updated the main comment to reflect that

[isagoico]

There was a misunderstanding - the issue is not reproducible anymore in build 1.1.18-1 on all environments.
Closing this 🎉

[thesahindia]

@isagoico , I believe the issue was fixed by this PR to close #6609 and the current issue which are basically the same. Can you please check that and update #6609 to reflect that it was reported by me.