[$250] Feature request - Show content when open deep link from other user profile which is not in contacts list reported by @aimane-chnaif

[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!

---

Problem:

It shows loading forever. Especially, when someone shares user profile link from other social app and open it, user gets confused.

Solution:

The page should show content. i.e. no access page, 404 page, or show "not in contacts" message and create new chat button, etc. At least should show close button to exit this page and go back to home screen.

Context/Examples/Screenshots/Notes:

infinite.loading.mp4

Platform:
Where is this issue occurring?

• Web
• iOS
• Android
• Desktop App
• Mobile Web
  Logs: https://stackoverflow.com/c/expensify/questions/4856
  Expensify/Expensify Issue URL:
  Issue reported by: @aimane-chnaif
  Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1666005837666169
  View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @lschurr (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

[lschurr]

I'm not super clear on what kind of links cause this problem. Adding eng for a second pair of eyes.

[melvin-bot]

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

[alex-mechler]

Are there any logs errors when this happens? Its possible that this is a bug and not a new feature

[aimane-chnaif]

@alex-mechler you can test with 2 accounts.
After login account A, open user profile with which doesn't have contact in account B.
Copy profile link and try to open it after login account B.

[alex-mechler]

Looks like there is no console errors from my limited testing. Seems useful that we would show / do anything other than an infinite loader here, but I'm not sure what yet. Doing some more digging / exploring before continuing

[alex-mechler]

Okay, after digging in more, properly loading the details for the user in this case would be quite a large amount of internal API work, so lets stick with showing an error growl and closing the modal.

Sending this external