[$500] "Unavailable workspace" appears when adding a member to a workspace

[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.16-3
Reproducible in staging?: y
Reproducible in production?: y
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: @puneetlath
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1703014430002699

Action Performed:

1. Login as account B in NewDot
2. Login as account A in OldDot
3. Add account B as member

Expected Result:

In the LHN workspace name should appear

Actual Result:

showed up in my LHN as “unavailable workspace”. Seems we are not sending the workspace info along with the pusher event that is sending the new room.

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

Recording.355.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01488edc00fcf10453
• Upwork Job ID: 1739005691185319936
• Last Price Increase: 2024-01-14

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01488edc00fcf10453

[melvin-bot]

Triggered auto assignment to @anmurali (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav (External)

[Famzy-codes]

Proposal

Please re-state the problem that we are trying to solve in this issue.

I've thoroughly reviewed the technical details regarding the missing display of workspace names in the LHN (Left Hand Navigation). This discrepancy occurs when adding account B as a member, resulting in the workspace name appearing as "unavailable workspace" instead of the expected display.

1. Issue Reproduction:

   • Confirmed reproducibility in both staging and production environments (version 1.4.16-3).
   • Observed the discrepancy when adding account B as a member within the NewDot and OldDot interfaces.

2. Expected vs. Actual Behavior:

   • Expected: The workspace name should be prominently displayed in the LHN.
   • Actual: The workspace name appears as "unavailable workspace," indicating a failure in transmitting the workspace information with the pusher event related to new room creation.

What is the root cause of that problem?

• The investigation revealed a gap in transmitting workspace details during the pusher event associated with room creation, leading to an absence of workspace name display in the LHN.

What changes do you think we should make in order to solve the problem?

• Analyze and update the code logic responsible for sending pusher events to include accurate workspace information.
• Verify that the workspace details are being correctly retrieved and transmitted during the account member addition process.
• Conduct comprehensive testing to ensure the proper display of workspace names in the LHN across supported platforms (MacOS: Chrome / Safari).

What alternative solutions did you explore? (Optional)

1. Code Review and Debugging:

   • Review the pusher event handling code segments.
   • Debug the code to trace the transmission of workspace details during room creation and account member addition.

2. Code Modification and Testing:

   • Implement necessary code changes to include accurate workspace information in pusher events.
   • Thoroughly test the updated functionality to ensure the correct display of workspace names in the LHN.

3. Quality Assurance and Release:

   • Perform rigorous testing across staging and production environments.
   • Validate the fix's effectiveness without introducing new issues.
   • Document the resolution process and coordinate the deployment of the updated version.

[melvin-bot]

📣 @Famzy-codes! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[Tony-MK]

@Famzy-codes, You should use the Proposal Template and read the contribution guides for details on contributing.