Task - Chat header turns to skeleton after assigning task to user with no chat history

[m-natarajan]

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: 1.4.74-1
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail: exp around https://expensify.testrail.io/index.php?/tests/view/4561795&group_by=cases:section_id&group_id=291936&group_order=asc
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

1. Go to staging.new.expensify.com and login
2. Go to FAB > Assign task.
3. Assign a task to a user that has no chat history.

Expected Result:

After the task is created, the chat header will not show skeleton.

Actual Result:

After the task is created, the chat header shows skeleton.

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6482493_1715848404484.20240516_163050.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @aldo-expensify

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

1. If you find which PR caused the issue/bug, you can reassign it to the person responsible for it.
   • If the author is OOO or won’t get online before the daily deploy is due, you are responsible for finding the best fix/path forward. Don’t hesitate to ask for help!
2. Try to reproduce the issue, if the bug is on production, remove the DeployBlocker label but stay assigned to fix it (or find out which PR broke it to get help from the author).
   • You can adjust the urgency of the issue to better represent the gravity of the bug.
   • If the issue is super low priority, feel free to un-assign yourself.
   • Be careful with PHP warnings, sometimes it is more complex than just adding a null coalescing operator as they might be uncovering some bigger bug.
   • If it was a one-off issue that requires no action (for example, Bedrock was down or it is a duplicated issue), you can close it.

Remember rule #2: Never un-assign yourself from a real DeployBlocker unless you are 100% sure someone else is assigned and will take care of it.

[github-actions]

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

[m-natarajan]

@kadiealexander FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[m-natarajan]

We think that this bug might be related to #vip-vsb

[iwiznia]

I can't reproduce this. It's possible it was during when we had issues in the servers, can you re-test please @m-natarajan?

[kadiealexander]

Requested a retest here: https://expensify.slack.com/archives/C9YU7BX5M/p1715922013205569

[kavimuru]

Still able to reproduce by the tester in 2 different account.

rpreplay_final1715946448.mp4

rpreplay_final1715946288.mp4

[kadiealexander]

@iwiznia can you identify the offending PR for this one?

[aldo-expensify]

I'm trying to reproduce, but failing. I tried creating a task for a user that doesn't exist and I also tried creating a task for a user with whom I opened a chat first (no messages in the chat). In both cases, it worked fine:

Screen.Recording.2024-05-22.at.12.15.13.PM.mov

[aldo-expensify]

Can't reproduce in dev either

[mountiny]

Seems like we are not able to reproduce, this does not seem like a web blocker to me so going to remove the label

[melvin-bot]

@kadiealexander, @aldo-expensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

[aldo-expensify]

I'm working on fixing this now

[aldo-expensify]

Seems like CreateTask creates an onyx report with only 1 participant (yourself) missing the assignee and also a second update with both participants, so the second update fixes it:

Screen.Recording.2024-06-21.at.12.12.18.PM.mov

but then, there is a call to GetMissingOnyxMessages (which sounds like a something that shouldn't be happening) brings again the onyx report with the single participant causing the problem:

I'll first fix the report onyx update with incorrect participants. Then, I'll investigate why GetMissingOnyxMessages is getting called when it shouldn't.

[aldo-expensify]

PR up: https://github.com/Expensify/Auth/pull/11353

[aldo-expensify]

Not deployed yet, got confused. We need to retest once https://github.com/Expensify/Auth/pull/11353 is deployed. I'm not sure why I wasn't able to login into applausetester+kh040601@applause.expensifail.com (the account I was using to reproduce the bug)

[aldo-expensify]

@kadiealexander I'll go OOO next week, we will probably deploy around Monday... maybe then you can ping someone from applause to retest? 🙇

[kadiealexander]

Requested a retest here.

[kavimuru]

Able to reproduce

20240719_175437.mp4

[aldo-expensify]

Thanks @kavimuru . I'll have to investigate and see what else may be the issue.

[kadiealexander]

@aldo-expensify any updates here?

[aldo-expensify]

no, I haven't investigated again, I'll do it asap

[kadiealexander]

Not overdue

[aldo-expensify]

Investigating now....

[aldo-expensify]

Hmm I don't see "Assign task" anymore in the menu, so I can't reproduce with the existing steps... Should we close?

If you create a task from within a chat, then the "Assign task" action appears in the FAB (big green button) menu, but it appears with a pre-selected assignee, so we can't either reproduce this way.

[aldo-expensify]

I'll close this since I think it is no longer reproducible. Feel free to reopen if you find new steps to reproduce.