Repository navigation
[Due for payment 2025-06-02] [Due for payment 2025-05-30] Reports - Bottom modal does not close after tapping Move expenses #62502
Description
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.1.48-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check - New feature
If this was caught during regression testing, add the test name, ID and link from TestRail: #62270
Email or phone of affected tester (no customers): applausetester+sdsdjo@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Samsung Galaxy Z Fold 4 / Android 14
App Component: Search
Action Performed:
- Go to staging.new.expensify.com
- Go to workspace chat.
- Submit a manual expense.
- Go to Reports.
- Long press on the expense.
- Tap Select.
- Tap Move expenses.
Expected Result:
Bottom modal will close.
Actual Result:
Bottom modal does not close after tapping Move expenses.
On Android, the bottom modal closes after tapping Move expenses, but it reopens when tapping back button on move expenses page.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Activity
melvin-bot commentedon May 21, 2025
Triggered auto assignment to @alexpensify (
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.melvin-bot commentedon May 21, 2025
Triggered auto assignment to @yuwenmemon (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 21, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 21, 2025
👋 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:
nlemma commentedon May 21, 2025
@alexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
nabi-ebrahimi commentedon May 21, 2025
It doesn't show the
Move expensefor me. I followed your directions.yuwenmemon commentedon May 21, 2025
Hmmm... I'm not able to reproduce this
6 remaining items
[-]Reports - Bottom modal does not close after tapping Move expenses[/-][+][Due for payment 2025-05-30] Reports - Bottom modal does not close after tapping Move expenses[/+]melvin-bot commentedon May 23, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon May 23, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.50-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-05-30. 🎊
melvin-bot commentedon May 23, 2025
@yuwenmemon @alexpensify @yuwenmemon The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
[-][Due for payment 2025-05-30] Reports - Bottom modal does not close after tapping Move expenses[/-][+][Due for payment 2025-06-02] [Due for payment 2025-05-30] Reports - Bottom modal does not close after tapping Move expenses[/+]melvin-bot commentedon May 26, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.51-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-06-02. 🎊
melvin-bot commentedon May 26, 2025
@yuwenmemon @alexpensify @yuwenmemon The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]