Android - Start chat - Huge spacing between bottom button and offline indicator

[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.0.67-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team

Action Performed:

Precondition:

• Device navigation is buttons instead of swipe gestures.

1. Launch ND or hybrid.
2. Go offline.
3. Open FAB > Start chat.
4. Tap Add to group next to any user.
5. Note that there is huge spacing between Next button and offline indicator.
6. Go to #room.
7. Note that there is huge spacing between Create room button and offline indicator.

Expected Result:

There should not be huge spacing between bottom button and offline indicator.

Actual Result:

There is huge spacing between bottom button and offline indicator.

This issue is not reproducible if device navigation uses swipe gestures.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6677723_1732690886970.Screen_Recording_20241127_145424_Settings.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

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

[mountiny]

Its from the edge-to-edge PR cc @kirillzyusko @chrispader

[mountiny]

discussing in the linked thread

[kirillzyusko]

@chrispader is going to take this over (according to Slack conversation)