Unavailable workspace displayed while waiting for API response

[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: Reproducible in staging?: Needs Reproduction Reproducible in production?: Needs Reproduction 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 Expensify/Expensify Issue URL: Issue reported by: @quinthar Slack conversation: https://expensify.slack.com/archives/C05LX9D6E07/p1723133790546149

Action Performed:

1. signing into accountA in #focus mode that is a member of a room that isn't currently read
2. sending a message in the room from accountB while accountA is still open in another browser
3. go offline in accountA
4. open the room and see what the header shows

Expected Result:

Workspace name and loading skeleton for the content while it loads

Actual Result:

No loading skeleton and unavailable workspace displayed until response received form Chronos comment

Workaround:

Unknown

Platforms:

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

• [x] Android: Native
• [ ] Android: mWeb Chrome
• [ ] iOS: Native
• [ ] iOS: mWeb Safari
• [X] MacOS: Chrome / Safari
• [ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/c53d236a-ecdd-474b-a934-8d301a265de9

View all open jobs on GitHub

[melvin-bot[bot]]

Current assignee @puneetlath is eligible for the AutoAssignerNewDotQuality assigner, not assigning anyone new.

[melvin-bot[bot]]

Current assignee @puneetlath is eligible for the Bug assigner, not assigning anyone new.

[MelvinBot]

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

[muttmuure]

I think we agreed that fixing issues with Chronos is out of scope for the NewDot Quality project: https://expensify.slack.com/archives/C05LX9D6E07/p1723207265131579

[melvin-bot[bot]]

Triggered auto assignment to @srikarparsi (AutoAssignerNewDotQuality)

[melvin-bot[bot]]

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

[muttmuure]

I can see we agreed to fix this one however - here: https://expensify.slack.com/archives/C05LX9D6E07/p1724072534751829?thread_ts=1723133790.546149&cid=C05LX9D6E07

[muttmuure]

I don't think it's necessarily related to Chronos, just to chats that take a long time to deliver an API response

[tsa321]

Maybe related to https://github.com/Expensify/App/issues/43656 because we decide to display the first message.

[melvin-bot[bot]]

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

[sakluger]

I'm adding another BZ team members since I'll be OOO through 8/30.

[Christinadobrzyn]

Trying these reproduction steps in the Slack chat:

1. signing into accountA in #focus mode that is a member of a room that isn't currently read
2. sending a message in the room from accountB while accountA is still open in another browser
3. go offline in accountA
4. open the room and see what the header shows

(accountA c.dobrzyn+17@gmail.com & accountB c.dobrzyn+45@expensifail.com)

This seems to happen with Chats and Rooms when offline. Here's a video of both. Updated the OP with these testing steps. I think this is the issue? @srikarparsi do you agree?

https://github.com/user-attachments/assets/100ee6e8-55d6-4614-85c5-a198b6983a1c

[srikarparsi]

Hey @Christinadobrzyn! I’m not sure if I missed it but was there an unavailable workspace subtitle in the video? I’ll also try looking more into what could be causing this tomorrow

[Christinadobrzyn]

Hi @srikarparsi, no- I didn't see the unavailable workspace, but the skeleton showed when first testing. I just tested again and the skeleton doesn't show and I don't see the unavailable workspace either.

[MelvinBot]

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

[srikarparsi]

Got it, didn't get time to try to reproduce this today but will try to make time for this tomorrow

[Christinadobrzyn]

I'm still not able to get that error. I wonder if we should just ask QA to retest this again or close until it's more clear how to reproduce it?

[sakluger]

@Christinadobrzyn I don't think QA was ever able to reproduce this one.

@quinthar we're having a hard time reproducing the issue. Are you still seeing this issue in your account?

[melvin-bot[bot]]

@sakluger @srikarparsi @Christinadobrzyn this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[muttmuure]

Can we amend the reproduction steps to:

1. Enable 4G throttling
2. Send a message to Chronos
3. Before you get your response from Chronos open a room

[melvin-bot[bot]]

@sakluger, @srikarparsi, @Christinadobrzyn Eep! 4 days overdue now. Issues have feelings too...

[Christinadobrzyn]

heads up - I'm going to be ooo 9/4-9/11.

I tried these steps in browserstack Android and I can't reproduce the error. @muttmuure where are you getting the error in those steps? In the new room or in Chronos?

[srikarparsi]

We weren't able to reproduce this in the thread and I wasn't able to reproduce this locally either. I'm going to keep an eye on the thread to see if it gets reproduced but going to close this out for now.

https://github.com/user-attachments/assets/46123b86-b592-469e-934d-c126b59a08b5