Skip to content

[Due for payment 2025-03-17] [Due for payment 2025-03-13] [$250] iOS - Search - Search page cannot be dismissed by swiping to the right #57291

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?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): applausetester+sj9032@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: iPhone 15 Pro Max / iOS 18.3
App Component: Search

Action Performed:

  1. Launch ND or hybrid app.
  2. Tap on the search icon on the top right
  3. Swipe to the right to dismiss the search page (iOS swiping style)

Expected Result:

The search page can be dismissed by swiping to the right (previously it was fixed in #51731)

Actual Result:

The search page cannot be dismissed by swiping to the right.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6750749_1740219577904.20250222_181417.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021894676272056100014
  • Upwork Job ID: 1894676272056100014
  • Last Price Increase: 2025-02-26
  • Automatic offers:
    • DylanDylann | Reviewer | 106292983
    • nkdengineer | Contributor | 106292984
Issue OwnerCurrent Issue Owner: @JmillsExpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 22, 2025
  2. melvin-bot commented on Feb 22, 2025

    @melvin-bot

    Triggered auto assignment to @JmillsExpensify (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. nkdengineer commented on Feb 22, 2025

    @nkdengineer
    Contributor

    🚨 Edited by proposal-police: This proposal was edited at 2025-02-22 20:02:26 UTC.

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    The search page cannot be dismissed by swiping to the right.

    What is the root cause of that problem?

    It starts to happen after this PR, we removed swipeDirection that returned from getModalStyles and replaced it with swipeDirection prop

    https://github.com/Expensify/App/pull/55157/files#diff-c5dd0a065b12f253786ab2916473640a80014957475696db4d97bedc23f47af2L158

    swipeDirection,

    And we don't pass swipeDirection prop here.

    It may aslo happen with other modal that has propagateSwipe is true

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

    Pass the swipeDirection as right here. We need to check for other places that propagateSwipe is true and pass swipeDirection prop accordingly if it happens

    What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

    It's just missing a prop for swipe action so I think we can skip the test

    What alternative solutions did you explore? (Optional)

    We can still get the swipeDirection from getModalStyles and fallback it here if swipeDirection prop is undefined

    StyleUtils.getModalStyles(

    Or we can add the default value for swipeDirection

    Or we can remove swipeDirection prop and still get swipeDirection from getModalStyles because I don't see we pass this prop anywhere

    Result

    Screen.Recording.2025-02-23.at.02.58.28.mov

    Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Feb 26, 2025
  5. changed the title [-]iOS - Search - Search page cannot be dismissed by swiping to the right[/-] [+][$250] iOS - Search - Search page cannot be dismissed by swiping to the right[/+] on Feb 26, 2025
  6. melvin-bot commented on Feb 26, 2025

    @melvin-bot
  7. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 26, 2025
  8. melvin-bot commented on Feb 26, 2025

    @melvin-bot

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

  9. JmillsExpensify commented on Feb 26, 2025

    @JmillsExpensify
    Contributor

    Opened up to the community

  10. 24 remaining items

  11. changed the title [-][Due for payment 2025-03-13] [$250] iOS - Search - Search page cannot be dismissed by swiping to the right[/-] [+][Due for payment 2025-03-17] [Due for payment 2025-03-13] [$250] iOS - Search - Search page cannot be dismissed by swiping to the right[/+] on Mar 10, 2025
  12. melvin-bot commented on Mar 10, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.10-6 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 2025-03-17. 🎊

    For reference, here are some details about the assignees on this issue:

  13. melvin-bot commented on Mar 10, 2025

    @melvin-bot

    @DylanDylann @JmillsExpensify @DylanDylann The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero 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]

  14. DylanDylann commented on Mar 17, 2025

    @DylanDylann
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: This is a new improvement, not a bug

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion:

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Test:

    1. Tap on the search icon on the top right
    2. Swipe to the right to dismiss the search page
    3. Verify that: The search page can be dismissed by swiping to the right

    Do we agree 👍 or 👎

  15. garrettmknight commented on Mar 17, 2025

    @garrettmknight
    Contributor

    Payment summary:

  16. melvin-bot commented on Mar 18, 2025

    @melvin-bot

    @JmillsExpensify Eep! 4 days overdue now. Issues have feelings too...

  17. melvin-bot commented on Mar 19, 2025

    @melvin-bot

    @JmillsExpensify Huh... This is 4 days overdue. Who can take care of this?

  18. JmillsExpensify commented on Mar 19, 2025

    @JmillsExpensify
    Contributor

    Regression test created.

  19. moved this from Bugs and Follow Up Issues to Done in #expensify-bugson Mar 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions