Skip to content

[Due for payment 2026-11-28] iPhone Duo - Spend - Blank space is shown at the footer in selection mode #107223

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.5.41-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: -
Email or phone of affected tester (no customers): joinsdjosjdojosijdiosnj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iPhone Duo / iOS 27.2
App Component: Search

Action Performed:

  1. Launch Expensify app.
  2. Go to workspace chat.
  3. Create an expense.
  4. Go to Spend > Expenses.
  5. Long tap on the expense and select it.

Expected Result:

No blank space will be shown at the footer.

Actual Result:

Blank space is shown at the footer in selection mode.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7317326_1794975303399.ScreenRecording_11-18-2026_12-10-49_1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7317326

Issue OwnerCurrent Issue Owner: @truph01

Activity

  1. applause-bot commented on Nov 18, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/244bc81c6d8a40eff9bf2d0d4765745a48ce8fb5f61901abfe46c2fb4e98abc6

  2. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 18, 2026
  3. expensify-chore-bot commented on Nov 18, 2026

    @expensify-chore-bot

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

  4. expensify-chore-bot commented on Nov 18, 2026

    @expensify-chore-bot

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

  5. github-actions commented on Nov 18, 2026

    @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. jponikarchuk commented on Nov 18, 2026

    @jponikarchuk

    We couldn't reproduce this issue a second time because it is device-specific, and the iPhone Duo is the only one in the team.

  7. MelvinBot commented on Nov 18, 2026

    @MelvinBot
    Contributor

    Proposal

    Likely causing PR: fix: add iPhone Duo support — medium confidence. It is included in the 9.5.41-0 staging release.

    What is the root cause of that problem?

    The expense footer reserves space for a horizontal bottom tab bar even when Duo displays the tabs vertically. That leaves phantom bottom padding.

    Supporting evidence

    The bottom-offset assumption predates this PR; the likely regression is introducing vertical-tab support without updating its spacing consumers.

    Verification limit: Not independently reproduced. QA could not reproduce it a second time, and web testing cannot establish native UIKit behavior. The recording’s actual insets and gap height remain unverified.

    What changes do you think we should make in order to solve the problem?

    Recommend rolling forward: make shared iOS bottom coverage account for vertical tabs, removing only the horizontal-tab reservation while preserving legitimate safe-area spacing.

    Validate selection-mode footers, list-end spacing, offline indicators, and floating buttons on the affected device, including orientation changes.

    What alternative solutions did you explore? (Optional)

    Reverting the Duo-support PR would also remove its intended navigation fixes. A targeted spacing correction is preferable, subject to native-device confirmation.


    Next Steps for Contributor+ team:
    To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/107223) to create a draft PR.
    To refine: @MelvinBot <your feedback>
    To reject: Explain why you are rejecting Melvin's proposal.


    view run

  8. melvin-bot commented on Nov 18, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  9. self-assigned this
    on Nov 18, 2026
  10. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Nov 18, 2026
  11. mountiny commented on Nov 18, 2026

    @mountiny
    Contributor

    This is on iphone due, not gonna block on it

  12. changed the title [-]iPhone Duo - Spend - Blank space is shown at the footer in selection mode[/-] [+][Due for payment 2026-11-28] iPhone Duo - Spend - Blank space is shown at the footer in selection mode[/+] on Nov 21, 2026
  13. melvin-bot commented on Nov 21, 2026

    @melvin-bot

    @truph01

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.51-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-11-28. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

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

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions