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
[$250] Hybrid - Android - Room - Big empy space displayed below composer when new room is created #57271
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:
Open the Expensify app.
Tap on the FAB and select "Create Chat"
Tap on "Room" and finish the creation flow.
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.
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…’”)
@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
Activity
melvin-bot commentedon Feb 22, 2025
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 commentedon Feb 24, 2025
@IuliiaHerets any idea why this was labeled as DeployBlocker and not DeployBlockerCash?
IuliiaHerets commentedon Feb 24, 2025
@MonilBhavsar I put
DeployBlockerCashlabel because the issue was not repro with staging server offscreen-20250222-063311.mp4
MonilBhavsar commentedon Feb 24, 2025
Makes sense. Looks like the label added was
Deployblockerwhere you wanted to putDeployBlockerCash, right?melvin-bot commentedon Feb 24, 2025
Triggered auto assignment to @marcochavezf (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Feb 24, 2025
💬 A slack conversation has been started in #expensify-open-source
8 remaining items
melvin-bot commentedon Feb 24, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ZhenjaHorbach (
External)marcochavezf commentedon Feb 24, 2025
The deploy checklist doesn't correspond to this version. The deploy checklist corresponds to this one.
marcochavezf commentedon Feb 24, 2025
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 commentedon Feb 24, 2025
It's possible the bug is not happening, @IuliiaHerets can you re-test, please?
melvin-bot commentedon Feb 24, 2025
Current assignee @mallenexpensify is eligible for the Bug assigner, not assigning anyone new.
IuliiaHerets commentedon Feb 24, 2025
@MonilBhavsar No, you confused me a bit and I made a typo in the comment, we put exactly
DeployBlockerlabel if the issue is not reproduced in staging with SS offIuliiaHerets commentedon Feb 24, 2025
@marcochavezf Tester can't repro the issue in the latest build (9.1.5-0)
screen-20250224-194102.mp4
marcochavezf commentedon Feb 24, 2025
Oh cool, thanks @IuliiaHerets for the testing! We can close it out