Open lanitochka17 opened 2 days ago
Triggered auto assignment to @chiragsalian (DeployBlockerCash
), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.
💬 A slack conversation has been started in #expensify-open-source
:wave: 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:
Job added to Upwork: https://www.upwork.com/jobs/~021854253987246789716
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (External
)
Issue has mentioned, Reproducible in production?: Y
But from the production video i don't see the same bug. Either way, feel like quite the edge case on a single platform so it doesn't feel deploy blocker worthy to me. Removing blocker label.
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.58.0 Reproducible in staging?: Y Reproducible in production?: Y If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Email or phone of affected tester (no customers): applausetester+ck102924@applause.expensifail.com Issue reported by: Applause - Internal Team
Action Performed:
Precondition: Main user has added copilot accounts (full & limited access)
Expected Result:
Account switcher should always be displayed in settings page even after forcekill & reopen app
Actual Result:
Account switcher disappears in settings page when forcekill & reopen app
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
https://github.com/user-attachments/assets/0deb7d17-fbc9-4712-8b45-c65c0373b94e
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @sobitneupane