Skip to content

[Due for payment 2026-10-30] [Requires Insights Beta] Android & iOS - Bottom tab - Page does not scroll to top after tapping Inbox and Insights tab #104284

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.13-1
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: #101339
Email or phone of affected tester (no customers): jsoidjndoiniodnsjojd@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iPhone 17 Pro Max / iOS 27.0.1
App Component: Other

Action Performed:

Precondition:

  • Account has many reports, expenses and workspaces.
  • Enable insightsPage beta.
  1. Launch Expensify app.
  2. On Home tab, scroll down.
  3. Tap Home tab.
  4. Repeat Step 2 and 3 with Inbox, Spend, Insights and Workspaces tab.

Expected Result:

Page will scroll to the top after tapping on Home, Inbox, Spend, Insights and Workspaces tab.

Actual Result:

Page does not scroll to the top after tapping on Inbox and Insights.

This issue does not occur on Home, Spend and Workspaces tab.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7288352_1792173787602.ScreenRecording_10-17-2026_01-58-00_1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7288352

Issue OwnerCurrent Issue Owner: @ZhenjaHorbach

Activity

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

  3. melvin-bot commented on Oct 16, 2026

    @melvin-bot

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

  4. melvin-bot commented on Oct 16, 2026

    @melvin-bot

    @grgia @ZhenjaHorbach you have been assigned to this deploy blocker because you reviewed the offending PR: #101339

  5. melvin-bot commented on Oct 16, 2026

    @melvin-bot

    @sumo-slonik you have been assigned to this deploy blocker because you authored the offending PR: #101339

  6. melvin-bot commented on Oct 16, 2026

    @melvin-bot

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

  7. github-actions commented on Oct 16, 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. ZhenjaHorbach commented on Oct 16, 2026

    @ZhenjaHorbach
    Contributor

    To reproduce, need beta feature
    Can be demoted

  9. 16 remaining items

  10. war-in commented on Oct 19, 2026

    @war-in
    Contributor

    @Expensify/design We'd love your input on this one 🙏

    When a user taps the tab they're already on, should the screen automatically scroll to the top? This is react-navigation's default behavior, but we can disable it with a patch if we'd rather not have it.

    Below is a comparison of the behavior with and without scroll-to-top. (Note: this is a dev build, so there's a lag that won't be present in production.)

    Screen_Recording_20261019_134741_Expensify.Dev.mp4
  11. dannymcclain commented on Oct 19, 2026

    @dannymcclain
    Contributor

    When a user taps the tab they're already on, should the screen automatically scroll to the top?

    I'm personally a fan of this interaction, so I'm down to keep it/make it work on all the tabs.

  12. shawnborton commented on Oct 19, 2026

    @shawnborton
    Contributor

    Totally agree! For Workspaces, I think the second tap might even act like a back button, right? Basically if you were nested in the Workspace Editor, tapping the Workspace tab might bring you back to the Workspaces list.

  13. dannymcclain commented on Oct 19, 2026

    @dannymcclain
    Contributor

    For Workspaces, I think the second tap might even act like a back button, right? Basically if you were nested in the Workspace Editor, tapping the Workspace tab might bring you back to the Workspaces list.

    Yes! 100% agree with that. That seems to be how it currently is working on mobile staging, and I think it's good:

    ScreenRecording_10-19-2026.08-08-44_1.MP4
  14. war-in commented on Oct 19, 2026

    @war-in
    Contributor

    Thank you! It'll be fixed in this PR - #104368 if you want to give it a try

  15. dubielzyk-expensify commented on Oct 19, 2026

    @dubielzyk-expensify
    Contributor

    Agree with all that! Huge fan of those native shortcuts

  16. changed the title [-][Requires Insights Beta] Android & iOS - Bottom tab - Page does not scroll to top after tapping Inbox and Insights tab[/-] [+][Due for payment 2026-10-30] [Requires Insights Beta] Android & iOS - Bottom tab - Page does not scroll to top after tapping Inbox and Insights tab[/+] on Oct 23, 2026
  17. melvin-bot commented on Oct 23, 2026

    @melvin-bot

    @ZhenjaHorbach

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.18-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-10-30. 🎊

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

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions