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
Expense - Empty space is created between composer and report fields on track expense. #71419
Once redirected to chat, open the just created expense.
Note that an empty space is visible between composer and report fields.
Expected Result:
No empty space should be visible at the bottom of report on track expenses, between composer and report fields.
Actual Result:
An empty space is generated at the bottom of the report on track expenses, between composer and report fields. Issue is also reproducible on expenses submitted to 1:1 conversations.
👋 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.
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.2.19-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: https://test-management.browserstack.com/projects/2219752/test-runs/TR-962/folder/13176877/41237350/920382630
Email or phone of affected tester (no customers): ibellicotest+1852@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app)
App Component: Money Requests
Action Performed:
Prerequisite: Account has a Self DM.
Expected Result:
No empty space should be visible at the bottom of report on track expenses, between composer and report fields.
Actual Result:
An empty space is generated at the bottom of the report on track expenses, between composer and report fields. Issue is also reproducible on expenses submitted to 1:1 conversations.
Workaround:
Unknown
Platforms:
Screenshots/Videos
11.mp4
View all open jobs on GitHub