Open lanitochka17 opened 4 hours ago
: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:
Triggered auto assignment to @NikkiWines (DeployBlockerCash
), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.
💬 A slack conversation has been started in #expensify-open-source
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.54.1 Reproducible in staging?: Y Reproducible in production?: N If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: 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/5134614 Issue reported by: Applause - Internal Team
Action Performed:
precondition:
Expected Result:
User is able to open any report, search, account settings and FAB
Actual Result:
The app becomes unresponsive, unable to open any chat, search, account settings and FAB until the app is reopened
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/364fab69-5a95-460b-8d5c-ac43ad42b056
https://github.com/user-attachments/assets/a9f6bb65-5f6d-416a-8077-7b3348b0e65e
View all open jobs on GitHub