You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-05-28] [Due for payment 2025-05-27] Reports - Composer is blocked by bottom tab when expense report is opened from transaction thread #62196
Version Number: 9.1.46-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail:#61774 Email or phone of affected tester (no customers):applausetester+x31@applause.expensifail.com Issue reported by: Applause Internal Team Device used: iPhone 15 Pro Max / iOS 18.4 App Component: Search
Action Performed:
Launch Expensify app.
Go to workspace chat.
Submit two expenses to the workspace chat.
Go to Reports.
Open one of the expenses from Step 3.
Tap on the report header subtitle.
Expected Result:
The composer in the expense report will not be blocked by the bottom tab.
Actual Result:
The composer in the expense report is blocked by the bottom tab.
We can see a small part of the composer above the bottom tab, which shows that it is blocked.
👋 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:
Identify the pull request that introduced this issue and revert it.
changed the title [-]Reports - Composer is blocked by bottom tab when expense report is opened from transaction thread[/-][+][Due for payment 2025-05-27] Reports - Composer is blocked by bottom tab when expense report is opened from transaction thread[/+]on May 20, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.46-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@dukenv0307@bfitzexpensify@dukenv0307 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]
changed the title [-][Due for payment 2025-05-27] Reports - Composer is blocked by bottom tab when expense report is opened from transaction thread[/-][+][Due for payment 2025-05-28] [Due for payment 2025-05-27] Reports - Composer is blocked by bottom tab when expense report is opened from transaction thread[/+]on May 21, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.47-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@dukenv0307@bfitzexpensify@dukenv0307 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]
Activity
melvin-bot commentedon May 16, 2025
Triggered auto assignment to @mountiny (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 16, 2025
Triggered auto assignment to @bfitzexpensify (
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 16, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 16, 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:
adamgrzybowski commentedon May 16, 2025
I will take a look at that
adamgrzybowski commentedon May 16, 2025
@jponikarchuk I can't reproduce this problem. I tried on the web and iOS native. Is there something missing from my reproduction steps?
Screen.Recording.2025-05-16.at.14.43.21.mov
15 remaining items
[-]Reports - Composer is blocked by bottom tab when expense report is opened from transaction thread[/-][+][Due for payment 2025-05-27] Reports - Composer is blocked by bottom tab when expense report is opened from transaction thread[/+]melvin-bot commentedon May 20, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon May 20, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.46-12 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-27. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 20, 2025
@dukenv0307 @bfitzexpensify @dukenv0307 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]
mountiny commentedon May 20, 2025
Part of the project, we can close this one out as the regression testing and payments will be handled as part of traditional reports project
[-][Due for payment 2025-05-27] Reports - Composer is blocked by bottom tab when expense report is opened from transaction thread[/-][+][Due for payment 2025-05-28] [Due for payment 2025-05-27] Reports - Composer is blocked by bottom tab when expense report is opened from transaction thread[/+]melvin-bot commentedon May 21, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.47-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-05-28. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 21, 2025
@dukenv0307 @bfitzexpensify @dukenv0307 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]