[$250] Hybrid - Android - Room - Big empy space displayed below composer when new room is created

[IuliiaHerets]

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.1.4-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12
App Component: Chat Report View

Action Performed:

1. Open the Expensify app.
2. Tap on the FAB and select "Create Chat"
3. Tap on "Room" and finish the creation flow.
4. Check the composer behaviour and the space below it, when redirected to the new created room.

Expected Result:

Composer should be displayed at the bottom of the screen when the new room conversation is created.

Actual Result:

Big empty space is displayed below the composer when a new room is created.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6750486_1740181192360.Compose.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021894116929176870819
• Upwork Job ID: 1894116929176870819
• Last Price Increase: 2025-02-24

Issue Owner

Current Issue Owner: @ZhenjaHorbach

[melvin-bot]

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

[MonilBhavsar]

@IuliiaHerets any idea why this was labeled as DeployBlocker and not DeployBlockerCash?

[IuliiaHerets]

@MonilBhavsar I put DeployBlockerCash label because the issue was not repro with staging server off

screen-20250222-063311.mp4

[MonilBhavsar]

Makes sense. Looks like the label added was Deployblocker where you wanted to put DeployBlockerCash, right?

[melvin-bot]

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

[melvin-bot]

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

[github-actions]

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

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021894116929176870819

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @ZhenjaHorbach (External)

[marcochavezf]

Check out the open StagingDeployCash deploy checklist

The deploy checklist doesn't correspond to this version. The deploy checklist corresponds to this one.

[marcochavezf]

A likely culprit is #57110 (“Adjust adaptStateIfNecessary to push a split navigator without a sidebar screen”). But then it was reverted in the PR #57320 (“[CP Staging] Revert ‘Adjust adaptStateIfNecessary…’”)

[marcochavezf]

It's possible the bug is not happening, @IuliiaHerets can you re-test, please?

[melvin-bot]

Current assignee @mallenexpensify is eligible for the Bug assigner, not assigning anyone new.

[IuliiaHerets]

@MonilBhavsar No, you confused me a bit and I made a typo in the comment, we put exactly DeployBlocker label if the issue is not reproduced in staging with SS off

[IuliiaHerets]

@marcochavezf Tester can't repro the issue in the latest build (9.1.5-0)

screen-20250224-194102.mp4

[marcochavezf]

Oh cool, thanks @IuliiaHerets for the testing! We can close it out