Skip to content

Expense - Empty space is created between composer and report fields on track expense. #71419

Description

@jponikarchuk

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.

  1. Open the Expensify app.
  2. Tap on FAB and select "Create Expense"
  3. Create a manual expense and submit it to Self DM.
  4. Once redirected to chat, open the just created expense.
  5. 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.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

11.mp4

Image

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 27, 2025
  2. melvin-bot commented on Sep 27, 2025

    @melvin-bot

    Triggered auto assignment to @zanyrenney (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.

  3. melvin-bot commented on Sep 27, 2025

    @melvin-bot

    Triggered auto assignment to @neil-marcellini (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Sep 27, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Sep 27, 2025

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. VickyStash commented on Sep 29, 2025

    @VickyStash
    Contributor

    I think this is expected behaviour after #71084 is merged, it was discussed before here and here in the slack.
    cc @shawnborton

  7. shawnborton commented on Sep 29, 2025

    @shawnborton
    Contributor

    Correct, this is intentional now. I'm going to close as it's not a blocker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringHourlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions