Skip to content

[$500] Workspace - Unable to open settings on a policy disabled account #35802

Description

@izarutskaya

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.36.0
Reproducible in staging?: Y
Reproducible in production?: N
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: Applause-Internal Team
Slack conversation:

Action Performed:

  1. Log in as applausetester+disabledpolicy@applause.expensifail.com
  2. Open preferences and go offline
  3. Go back to LHN
  4. Click on the "Settings" button
  5. Create a new workspace with the top right "New workspace" button
  6. Click on the "Chats" button
  7. Open preferences and go online
  8. Go back to LHN
  9. Wait until the workspace chats disappear
  10. Click on the "Choose a workspace" button - "Expensify"
  11. Click on the "Choose a workspace" button - "Workspace with a red dot"
  12. Click on the "Choose a workspace" button
  13. Click away to close it
  14. Click on the "Settings" tab

Expected Result:

I should be albe to navigate to the settings tab.

Actual Result:

I get a "Hmm... it's not here" error when clicking on "Settings". I could repro it with other normal accounts too with different steps regarding the workspace but it didn't show up every time there.

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

Bug6367051_1707079312296.bandicam_2024-02-03_06-33-53-861.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~016b7315d221412f0b
  • Upwork Job ID: 1754455245810069504
  • Last Price Increase: 2024-02-05

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 5, 2024
  2. changed the title [-]Workspace - Unable to open settings on a policy disabled account[/-] [+][$500] Workspace - Unable to open settings on a policy disabled account[/+] on Feb 5, 2024
  3. melvin-bot commented on Feb 5, 2024

    @melvin-bot
  4. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 5, 2024
  5. melvin-bot commented on Feb 5, 2024

    @melvin-bot

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

  6. melvin-bot commented on Feb 5, 2024

    @melvin-bot

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

  7. github-actions commented on Feb 5, 2024

    @github-actions
    Contributor

    👋 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.
  8. melvin-bot commented on Feb 5, 2024

    @melvin-bot

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

  9. izarutskaya commented on Feb 5, 2024

    @izarutskaya
    Author

    We think that this bug might be related to #wave8-collect-admins
    CC @zanyrenney

  10. Gonals commented on Feb 5, 2024

    @Gonals
    Contributor

    @izarutskaya, I'm trying to follow the steps, but:

    Wait until the workspace chats disappear

    This one never happens for me. Do you get any errors in the console (or anywhere)?

  11. Gonals commented on Feb 5, 2024

    @Gonals
    Contributor

    I've tried with a couple of test accounts and haven't seen the issue. I can't log in with applausetester+disabledpolicy@applause.expensifail.com, though (Gmail is not letting me in)

  12. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Feb 5, 2024
  13. mountiny commented on Feb 5, 2024

    @mountiny
    Contributor

    It seems like the policy creation has failed and this was the end results, if we can create policies though in general this should not be a blocker

  14. Gonals commented on Feb 7, 2024

    @Gonals
    Contributor

    Still unable to reproduce, so I think it might be a one-case scenario. Closing for now. Feel free to reopen if you disagree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions