Skip to content

Expenses-Attendee list not visible on landscape mode during edition and "Apply" is cutted off #107498

Open

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.43-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: #106067
Email or phone of affected tester (no customers): ibellicotest+3215@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app)
App Component: Search

Action Performed:

Prerequisite: Account has a workspace with "Rules" and "Attendee Tracking" enabled.
Prerequisite 2: At least two expenses available.

  1. Open the Expensify app.
  2. Navigate to "Spend" > "Expenses"
  3. Select more than one expense > Tap on dropdown menu > "Edit Multiple"
  4. Tap on "Attendees"
  5. Switch to landscape mode and tap on search input to display keyboard.
  6. Note that "Apply" button is cutted off by keyboard.
  7. Start typing any user´s Email on search input.
  8. Note that results are not visible while typing without closing keyboard,

Expected Result:

"Apply" button should be completelly visible while editing attendees field in ladnscape mode, and search results should be visible while typing.

Actual Result:

"Apply" button is cutted off by keyboard during "Attendees" field edition while in landscape mode, and search results are not visible while typing if keyboard is not dismissed.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7319459_1795127154012.Bulk_Edit.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Chandana Kiran
Bug ID: 7319459

Issue OwnerCurrent Issue Owner: @DylanDylann

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 20, 2026
  2. applause-bot commented on Nov 20, 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/32bd98b1872f1daeec55d361bdd432accf894eee9d96727038dad81e69bead84

  3. expensify-chore-bot commented on Nov 20, 2026

    @expensify-chore-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #106067

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

    @expensify-chore-bot

    @mountiny @ikevin127 you have been assigned to this deploy blocker because you reviewed the offending PR: #106067

  5. expensify-chore-bot commented on Nov 20, 2026

    @expensify-chore-bot

    @DylanDylann you have been assigned to this deploy blocker because you authored the offending PR: #106067

  6. expensify-chore-bot commented on Nov 20, 2026

    @expensify-chore-bot

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

  7. github-actions commented on Nov 20, 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.
  8. MelvinBot commented on Nov 20, 2026

    @MelvinBot
    Contributor

    Proposal

    What is the root cause of that problem?

    The affected flow was introduced by [CFI] Update the Edit multiple flow to use inline editing and dropdown down style rows. It replaced the full-page bulk attendee editor with a shared picker that uses a bottom sheet on native devices.

    Confidence: High in the introducing PR; medium in the exact clipping mechanism. The likely cause is insufficient space above the landscape keyboard for the picker’s header, search results, and non-shrinking Apply footer.

    Code and release evidence

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

    Recommend reverting the introducing PR as the conservative deploy-unblocking option and retaining DeployBlockerCash. A targeted layout fix has not been validated sufficiently to recommend rolling forward instead.

    For a roll-forward, first verify that search results remain visible and scrollable and Apply remains fully reachable in Android hybrid landscape with the keyboard open. Check rotation and the shared single-expense attendee picker too.

    What alternative solutions did you explore? (Optional)

    Restoring only the previous full-page bulk attendee editor would reduce scope compared with a complete revert. Fixing the shared sheet’s available-height handling could preserve the new UI, but requires native verification.

    Verification limitation: No runtime tests were performed. This invocation permits web testing only; web evidence would not establish Android hybrid keyboard behavior. No code or issue metadata was changed.


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


    view run

  9. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Nov 20, 2026
  10. mountiny commented on Nov 20, 2026

    @mountiny
    Contributor

    We should fix this but I think its too narrow of an edge case and they can change to portrait to process this

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

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions