Fix: GBR Missing In Chat After Workspace Change

Hey guys! Ever run into a quirky issue where something just doesn't show up when it's supposed to? We've got one here that's been bugging some users, and we're gonna dive deep into it. It's all about the Left Hand Navigation (LHN) in Expensify, specifically when the General Business Room (GBR) chat isn't showing up after you move a report to a different workspace. Let's get into the nitty-gritty and see what's going on!

The Mystery of the Missing GBR

So, the core of the issue is that after changing the workspace of a report, the General Business Room (GBR) chat doesn't always show up in the Left Hand Navigation (LHN) where it should. This can be super confusing, especially when you're trying to keep track of your reports and conversations. Imagine moving a document to a new folder, but the folder looks empty – frustrating, right? That's the kind of vibe we're dealing with here. This issue was spotted in version v9.2.27-1 and has been confirmed to be reproducible in both staging and production environments. This means it's not just a fluke; it's a real problem affecting users across different setups.

The issue was initially reported by the Applause Internal Team, which means it's been caught by professionals who are dedicated to ensuring the app runs smoothly. The affected tester used a Windows 10 machine with Chrome, pinpointing a specific environment where the issue occurs. But remember, software bugs can be sneaky and might show up in various forms across different platforms. Now, let’s break down the steps to reproduce this bug, so you can see exactly what’s happening and maybe even try it out yourself.

Steps to Reproduce the Issue

Okay, let's get practical. If you want to see this issue in action, here’s what you need to do. Follow these steps closely, and you'll likely see the GBR disappear just like it did for our testers.

1. Sign in with a new account: Start fresh. This ensures there are no lingering settings or data causing interference.
2. Create two workspaces: This is crucial. You need at least two workspaces to move reports between them.
3. Open any workspace chat: Pick one of the workspaces you just created and dive into its chat section.
4. Create two manual expenses: We need some expense reports to work with, so go ahead and create a couple of them.
5. Open the expense report: Now, open one of those expense reports you just made.
6. Change the workspace of the report: Here’s where the magic happens (or, well, the bug appears). Move the report from its original workspace to the other one.
7. Observe the workspace chat in LHN: This is the moment of truth. Check the Left Hand Navigation (LHN) to see if the GBR is displayed in the workspace you just moved the report to.

Expected vs. Actual Result

So, what should happen, and what actually happens? This is where we nail down the discrepancy that makes this a bug.

Expected Result

Ideally, after moving the report to a new workspace, the GBR should immediately appear in the Left Hand Navigation (LHN) of that workspace. This is intuitive – you move a report, and the corresponding chat should be right there, ready for you to continue your discussions. It's all about seamless navigation and keeping everything organized.

Actual Result

In reality, the GBR doesn't show up right away. Instead, it pulls a disappearing act and leaves you wondering where it went. The chat only reappears after you navigate away from the report and then back into the workspace. This extra step is a nuisance and can definitely disrupt your workflow. It's like expecting your keys to be on the hook by the door, but they're mysteriously in your pocket – not where they should be, and you have to make an extra effort to find them. As you can see in the provided screenshot, the GBR is conspicuously absent, highlighting the issue clearly.

The Hunt for a Workaround

Right now, there's no known workaround for this issue. That means users are stuck with the extra step of navigating out and back into the workspace to see the GBR. It's not the end of the world, but it's definitely a friction point. Finding a workaround is like finding a temporary bridge when the main road is closed – it helps you get to your destination, even if it's not the most direct route. In this case, we're still searching for that bridge.

Platform Impact

This bug seems to be a bit picky about where it shows up. So far, it’s been confirmed on:

• Windows: Chrome: This is where the issue was initially reported, so it's definitely present in this environment.

But here’s the thing – while it’s confirmed on Windows Chrome, the issue's status is still uncertain on other platforms. Here’s a quick rundown:

• [ ] Android: App
• [ ] Android: mWeb Chrome
• [ ] iOS: App
• [ ] iOS: mWeb Safari
• [ ] iOS: mWeb Chrome
• [x] Windows: Chrome
• [ ] MacOS: Chrome / Safari
• [ ] MacOS: Desktop

The unchecked boxes mean we still need to investigate whether the bug exists on these platforms. It’s like a detective piecing together clues – we have one solid piece of evidence (Windows Chrome), but we need to gather more to complete the picture. This is where thorough testing across different environments becomes crucial.

Visual Evidence: Screenshots/Videos

Sometimes, seeing is believing. A picture (or video) can really drive home the point when describing a bug. In this case, there’s a screenshot available that clearly shows the missing GBR. Visual aids like this are super helpful for developers because they provide a clear, immediate understanding of the issue. It’s like showing a doctor an X-ray – it gives them a direct view of the problem area.

You can check out the screenshot here:

https://github.com/user-attachments/assets/60040433-9fa0-4d2f-99d1-cd1095fefa72

Contributing and Getting Involved

If you're interested in helping out with issues like this (and we always appreciate extra hands!), there are a few ways you can get involved. Expensify has a fantastic community, and contributing is a great way to learn and make a difference.

Contributing Guidelines

First off, check out the contributing guidelines. This document is your roadmap to understanding how to contribute effectively. It covers everything from setting up your development environment to submitting your first pull request.

You can find the guidelines here:

https://github.com/Expensify/ReactNativeChat/blob/main/contributingGuides/CONTRIBUTING.md

Join the Slack Channel

For real-time collaboration and discussions, the Expensify Slack channel is the place to be. To join, you'll need to request an invitation by emailing contributors@expensify.com. Slack is where developers, testers, and contributors come together to brainstorm, share updates, and solve problems.

Explore Open Jobs on GitHub

If you're looking for more ways to contribute, you can explore the open jobs on GitHub. These are issues that are specifically marked as "Help Wanted," making them a great starting point for new contributors.

You can find the list of open jobs here:

https://github.com/Expensify/App/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+Wanted%22

Conclusion

So, that's the scoop on the missing GBR issue! It’s a quirky bug that causes the General Business Room chat to disappear from the Left Hand Navigation after a report’s workspace is changed. While there’s no workaround yet, understanding the steps to reproduce the issue and knowing the affected platforms helps us get closer to a solution. If you're keen to dive deeper and contribute, check out the contributing guidelines and join the Slack channel. Every bit of help counts!

For more information on contributing to open-source projects and best practices, check out this guide on GitHub. Happy coding, guys!