Skip to content

iOS - Swipe gesture is possible when swiping for the first time #78051

Closed

Description

@lanitochka17

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.2.82-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #76343
Email or phone of affected tester (no customers): isjdsoijsojnsiojisndj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: iPhone 15 Pro Max / iOS 26.1
App Component: Other

Action Performed:

  1. Launch Expensify app.
  2. Open FAB > Start chat.
  3. Swipe from Chat to Room.
  4. Swipe back from Room to Chat.

Expected Result:

Swipe gesture should be disabled.

Actual Result:

In Step 3, swipe gesture is possible when swiping for the first time.
In Step 4, after swiping, it cannot be swiped again.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7033178_1766088932190.20251219_041309.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 18, 2025
  2. melvin-bot commented on Dec 18, 2025

    @melvin-bot

    Triggered auto assignment to @laurenreidexpensify (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. github-actions commented on Dec 18, 2025

    @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.
  4. melvin-bot commented on Dec 18, 2025

    @melvin-bot

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

  5. melvin-bot commented on Dec 18, 2025

    @melvin-bot

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

  6. samranahm commented on Dec 18, 2025

    @samranahm
    Contributor

    Proposal

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

    iOS - Swipe gesture is possible when swiping for the first time

    What is the root cause of that problem?

    On iOS, react-native-tab-view's PanResponder not properly initialize with swipeEnabled: false on the first render, causing a issue where the first swipe gesture works before the setting takes effect.

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

    We should add key prop to the TopTab.Navigator component that includes both the navigator ID and the initial route name. This will ensure the navigator is properly mounted with the correct swipeEnabled configuration from the very first render.

    key={`${id}-${validInitialTab ?? 'default'}`}

    here

    <TopTab.Navigator
    /* eslint-disable-next-line react/jsx-props-no-spreading */
    {...rest}
    id={id}
    initialRouteName={validInitialTab}

    What alternative solutions did you explore? (Optional)

    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.

  7. mdneyazahmad commented on Dec 18, 2025

    @mdneyazahmad
    Contributor

    We can close this issue. This will be fixed after we update react-native-pager-view to v7.0.2. This is handled in this issue

  8. mjasikowski commented on Dec 19, 2025

    @mjasikowski
    Contributor

    Closing because of the comment above (and also just a UI issue, not a big deploy blocker)

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions