Repository navigation
Fix: return home URL with backTo param for invalid reportID in getRoute - #95637
Conversation
| getRoute: (reportID: string | undefined, reportActionID?: string, referrer?: string, backTo?: string) => { | ||
| if (!reportID) { | ||
| Log.warn('Invalid reportID is used to build the REPORT_WITH_ID route'); | ||
| return getUrlWithBackToParam(ROUTES.HOME, backTo); |
There was a problem hiding this comment.
I think it's fine to add new use of getUrlWithBackToParam in this func as it is already used inside this one
Codecov Report✅ Changes either increased or maintained existing code coverage, great job!
|
|
@eVoloshchak Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button] |
|
@lorretheboy, could you merge the latest main please? |
|
@eVoloshchak I merged main |
Reviewer Checklist
Screenshots/VideosAndroid: HybridAppN/A Android: mWeb ChromeScreen.Recording.2026-07-15.at.20.49.25.moviOS: HybridAppScreen.Recording.2026-07-15.at.20.43.52.moviOS: mWeb SafariScreen.Recording.2026-07-15.at.20.40.43.movMacOS: Chrome / SafariScreen.Recording.2026-07-15.at.20.44.10.mov |
|
🚧 mountiny has triggered a test Expensify/App build. You can view the workflow run here. |
|
🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
|
PR #95637 added a new getUrlWithBackToParam usage in ROUTES.ts, exceeding the allowed seatbelt count of 105 and failing ESLint on main. Co-authored-by: Cursor <cursoragent@cursor.com>
|
🚀 Deployed to staging by https://github.com/mountiny in version: 9.4.36-0 🚀
|
|
🤖 No help site changes required. I reviewed the changes in this PR against the help site articles under What this PR does: It's an internal bug fix. Why no docs update is needed: The help site documents user-facing product behavior — features, settings, workspaces, billing, integrations, and UI flows. This change is a purely internal navigation/routing fix with no change to any documented feature, tab, setting, label, or button. There is no user-facing behavior described in the help site that this alters, so no article requires an edit and no draft docs PR was created. @lorretheboy, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR |
|
🚀 Deployed to staging by https://github.com/mountiny in version: 9.4.38-0 🚀
|
Help site review: no changes requiredI reviewed the changes in this PR against Expensify's help site content under Why: This PR is a purely internal crash/error-handling fix. In None of this changes any documented feature, workflow, setting, button, tab, or user-facing behavior described in the help site. The behavior is invisible to end users (it silently avoids a broken/crashing navigation state), so there is nothing to add or correct in No draft PR has been created since no documentation changes are needed. @lorretheboy, please confirm this assessment. If you believe a user-facing behavior here should be documented, let me know and I'll create the draft help site PR. |
|
🚀 Deployed to staging by https://github.com/mountiny in version: 9.4.40-0 🚀
|
|
🤖 Help site review — no changes required I reviewed the changes in this PR and no updates to Expensify's help site files under Why: This is an internal crash/navigation fix. It makes There is no change to any user-facing feature, setting, tab, button, label, or documented workflow. Help site articles describe product features and end-user workflows, and none of those are altered here — the behavior change is limited to how the app handles a malformed report link internally. Since no help site changes are required, no draft PR was created. @lorretheboy, if you believe a help site update is warranted here, let me know and I'll create one. |
|
🚀 Deployed to production by https://github.com/yuwenmemon in version: 9.4.40-0 🚀
Bundle Size Analysis (Sentry): |
Explanation of Change
Fixed Issues
$ #95195
PROPOSAL: #95195 (comment)
Tests
Test 1
Test 2
Offline tests
QA Steps
Test 1
Test 2
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectiontoggleReportand notonIconClick)Avatar, I verified the components usingAvatarare working as expected)StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))npm run compress-svg)Avataris modified, I verified thatAvataris working as expected in all cases)Designlabel and/or tagged@Expensify/designso the design team can review the changes.mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps.Screenshots/Videos
Android: Native
android.mov
Android: mWeb Chrome
android-web.mov
iOS: Native
ios.mov
iOS: mWeb Safari
ios.web.mov
MacOS: Chrome / Safari
web.mov