search

Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.56k stars 2.9k forks source link

mWeb - Workspace - Second created workspace is grayed out everytime internet is turned off #52651

Open IuliiaHerets opened 2 hours ago

IuliiaHerets commented 2 hours ago

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: 9.0.63-0 Reproducible in staging?: Y Reproducible in production?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5230599&group_by=cases:section_id&group_order=asc&group_id=229067 Issue reported by: Applause Internal Team

Action Performed:

  1. Open the staging.new.expensify.com website.
  2. Turn off internet connection.
  3. Open workspace selector on the top left corner.
  4. Tap on the "+" button to create a new one.
  5. Tap on the arrow on the top left corner.
  6. Create a second one.
  7. Return to LHN.
  8. Verify both workspaces were created.
  9. Turn on internet connection.
  10. Verify both workspaces are not grayed out anymore.
  11. Turn on internet connection again.
  12. Verify both workspaces are not grayed out.

Expected Result:

Just created workspaces should remain in normal colour when turning internet connection off.

Actual Result:

When creating two workspaces while offline, the second one becomes grayed out everytime that internet connection is off.

Workaround:

Unknown

Platforms:

Screenshots/Videos

https://github.com/user-attachments/assets/b2cfc252-52f2-4be9-b11b-fc6ba25a368c

View all open jobs on GitHub

melvin-bot[bot] commented 2 hours ago

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