You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Reports - App crashes when navigating from "Unread" to "All" header #61340
Version Number: 9.1.39-2 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Email or phone of affected tester (no customers):nathanmulugetatesting+3671@gmail.com Issue reported by: Applause - Internal Team
Action Performed:
Navigate to staging.new.expensify.com
Create a workspace
Create an expense
Navigate to "Reports" then to "Chats"
Navigate to "Unread" header then back to "All"
Expected Result:
App opens All chats
Actual Result:
App crashes
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug6819758_1746203742480.bandicam_2025-05-02_19-28-49-673.mp4
👋 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:
Identify the pull request that introduced this issue and revert it.
react-dom.development.js:22873 Uncaught Invariant Violation: scrollToIndex should be used in conjunction with getItemLayout or onScrollToIndexFailed, otherwise there is no way to know the location of offscreen indices or handle failures.
at invariant (webpack-internal:///./node_modules/fbjs/lib/invariant.js:40:15)
at VirtualizedList.scrollToIndex (webpack-internal:///./node_modules/react-native-web/dist/vendor/react-native/VirtualizedList/index.js:181:64)
at FlatList.scrollToIndex (webpack-internal:///./node_modules/react-native-web/dist/vendor/react-native/FlatList/index.js:188:21)
at Object.eval [as scrollToIndex] (webpack-internal:///./src/components/Search/SearchList.tsx:175:21)
at eval (webpack-internal:///./src/hooks/useSearchHighlightAndScroll.ts:165:11)
at imperativeHandleEffect (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:16314:5)
at commitHookEffectListMount (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:23184:26)
at commitLayoutEffectOnFiber (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:23302:17)
at commitLayoutMountEffects_complete (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:24722:9)
at commitLayoutEffects_begin (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:24708:7)
eval @ SearchList.tsx:140
eval @ useSearchHighlightAndScroll.ts:150
Activity
melvin-bot commentedon May 2, 2025
Triggered auto assignment to @arosiclair (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon May 2, 2025
👋 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:
melvin-bot commentedon May 2, 2025
💬 A slack conversation has been started in #expensify-open-source
arosiclair commentedon May 2, 2025
Took a few tries, but I reproduced:
arosiclair commentedon May 2, 2025
Reproduced in dev:
arosiclair commentedon May 2, 2025
Reverting #60896 seems to fix it. cc @martasudol @c3024 @MariaHCD @mountiny
I'll prepare a revert PR
melvin-bot commentedon May 2, 2025
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.
arosiclair commentedon May 2, 2025
Working on CP: https://expensify.slack.com/archives/C07J32337/p1746214088096349
arosiclair commentedon May 2, 2025
All fixed!