Skip to content

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

Closed

Description

@IuliiaHerets

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.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): ibellicotest+294@gmail.com
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 OwnerCurrent Issue Owner: @ZhenjaHorbach

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Feb 22, 2025
  2. melvin-bot commented on Feb 22, 2025

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

  3. MonilBhavsar commented on Feb 24, 2025

    @MonilBhavsar
    Contributor

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

  4. IuliiaHerets commented on Feb 24, 2025

    @IuliiaHerets
    Author

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

    screen-20250222-063311.mp4
  5. MonilBhavsar commented on Feb 24, 2025

    @MonilBhavsar
    Contributor

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

  6. added
    DeployBlockerCashThis issue or pull request should block deployment
    and removed
    DeployBlockerIndicates it should block deploying the API
    on Feb 24, 2025
  7. melvin-bot commented on Feb 24, 2025

    @melvin-bot

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

  8. melvin-bot commented on Feb 24, 2025

    @melvin-bot

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

  9. 8 remaining items

  10. melvin-bot commented on Feb 24, 2025

    @melvin-bot

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

  11. marcochavezf commented on Feb 24, 2025

    @marcochavezf
    Contributor

    Check out the open StagingDeployCash deploy checklist

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

  12. marcochavezf commented on Feb 24, 2025

    @marcochavezf
    Contributor

    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…’”)

  13. marcochavezf commented on Feb 24, 2025

    @marcochavezf
    Contributor

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

  14. added
    BugSomething is broken. Auto assigns a BugZero manager.
    and removed
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 24, 2025
  15. melvin-bot commented on Feb 24, 2025

    @melvin-bot

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

  16. IuliiaHerets commented on Feb 24, 2025

    @IuliiaHerets
    Author

    @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

  17. IuliiaHerets commented on Feb 24, 2025

    @IuliiaHerets
    Author

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

    screen-20250224-194102.mp4
  18. marcochavezf commented on Feb 24, 2025

    @marcochavezf
    Contributor

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

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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions