-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Track expense - Back button returns to the same workspace chat after deleting track expense #56321
Comments
Triggered auto assignment to @trjExpensify ( |
Triggered auto assignment to @nkuoch ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 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:
|
Expense can't be deleted on production XRecorder_04022025_133323.mp4 |
Kind of a minor bug, not sure if this is worth blocking deploy on. Looks related to this PR: #55015 |
We reverted the offending PR. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.94-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp #56073
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: iPhone 15 Pro Max / iOS 18.2
App Component: Money Requests
Action Performed:
Expected Result:
App will return to self DM.
Actual Result:
App returns to the same workspace chat.
Only the second tap on the back button returns app to the self DM.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6732993_1738664512753.ScreenRecording_02-04-2025_18-17-59_1.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: