[Due for payment 2026-09-11] [Sentry: APP-KCV] Web TypeError navigation.setParams is not a function in useReportActionsNewActionLiveTail

@mallenexpensify

Sentry

https://expensify.sentry.io/issues/APP-KCV

Impact (snapshot at filing)

Users (total since first seen): 58
Events: 82
Users (last 14d): 59 (45 on 9.4.59-5, 13 on 9.4.60-2, 1 on 9.4.61-0)
First seen: 2026-08-24
Last seen: ongoing
Platform: web
App version(s): 9.4.59 – 9.4.61
Affected route(s) (parameterized): /r/:reportID/:reportActionID
Mechanism: generic (React passive effect, caught by an error boundary)

Stack trace (top frames, first-party only)

src/pages/inbox/report/useReportActionsNewActionLiveTail.ts:172
    navigation.setParams({reportActionID: ''});
react-dom-client.production.js (commitHookEffectListMount)
react-dom-client.production.js (commitPassiveMountOnFiber)
react-dom-client.production.js (recursivelyTraversePassiveMountEffects)

Suspected cause

The live-tail jump effect calls navigation.setParams(...) on the object returned by useNavigation(). setParams only exists on the navigation object of a screen. When the hook runs in a tree where useNavigation() resolves to a navigator rather than a screen, setParams is undefined and the effect throws.

The call was introduced in prevent live-tail cleanup from clearing RHP route params (merged 2026-08-21), which replaced the Navigation.setParams singleton call with the hook-derived navigation.setParams. The first Sentry event is 2026-08-24, so this looks like a regression from that PR.

Reproduction

Unknown — see Sentry events linked from the Sentry issue. All events are on the report route with a linked report action, so opening a deep link to a specific message and letting the report finish its initial load is the likely path.

Contributor+ Checklist:

[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

Link to the comment on the PR: prevent live-tail cleanup from clearing RHP route params #98020 (comment)
Link to the comment on the Issue:
[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: NA
[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.

I don't think we need a regression test for this one.

@mananjadhav

Claude posting on behalf of Matt:

$250 to @mananjadhav (Contributor+).


Contributor	Nothing due, @WojtekBoman is flagged Contractor by Melvin
Contributor+	@mananjadhav due $250 via NewDot, 100%
Job price	$250, standard, no price in title
Reduction	None
Increase	None
Blockers	1 linked, rebutted
Precedent	None needed, this is the standard path
Needs a ruling	No

To pay, copy this block and paste it into the comment box:

### Payment Summary
Contributor+: @mananjadhav due $250 via NewDot

How the amount is reached


PR	#99533, author @WojtekBoman
Size	5 files, +172 / -4
C+ checklist on this issue	Posted by @mananjadhav, all boxes checked
Reviewer checklist on the PR	Posted by @mananjadhav, all boxes checked
Platform evidence	5 of 5 boxes checked, 1 of 5 carries a video

Job price $250. No price in the title, so the standard amount applies.
Contributor: nothing due. Melvin flags @WojtekBoman as a Contractor.
Contributor+: 100%. The reviewer checklist carries test steps, so the missing-tests rule does not fire, and 5 files with +172 lines is not a minor edit.
No regression cut. #100006 was flagged against this PR and rebutted: @mountiny, "Demoting, I dont think this has to be a blocker". Melvin's own analysis found every file in that path byte-identical between production and staging.
No increase. 5 files and +172 lines sit below the 25 file and 1000 line thresholds.

Reported, not deducted: 1 of 5 platforms carries evidence on the reviewer checklist. A count for the record.

_{Claude posting on behalf of Matt. PAYRUBRICTEST v2}

@mountiny

@mountiny with this being a Sentry issue, do you want to wait a lil while longer before I pay out?

This seems to be resolved so you can pay out

@mananjadhav

Payment Summary

Contributor+: @mananjadhav due $250 via NewDot

@mananjadhav

$250 approved for @mananjadhav

Navigation Menu

Repository navigation

[Due for payment 2026-09-11] [Sentry: APP-KCV] Web TypeError navigation.setParams is not a function in useReportActionsNewActionLiveTail #99517

Sentry

Impact (snapshot at filing)

Stack trace (top frames, first-party only)

Suspected cause

Reproduction

Related

9 remaining items

Payment Summary

BugZero Checklist (@mallenexpensify)

Contributor+ Checklist:

Payment Summary

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[Due for payment 2026-09-11] [Sentry: APP-KCV] Web TypeError navigation.setParams is not a function in useReportActionsNewActionLiveTail #99517

Description

Sentry

Impact (snapshot at filing)

Stack trace (top frames, first-party only)

Suspected cause

Reproduction

Related

Activity

jponikarchuk commented on Sep 1, 2026

melvin-bot commented on Sep 2, 2026

melvin-bot commented on Sep 5, 2026

9 remaining items

melvin-bot commented on Sep 10, 2026

melvin-bot commented on Sep 10, 2026

Payment Summary

BugZero Checklist (@mallenexpensify)

mananjadhav commented on Sep 12, 2026

Contributor+ Checklist:

mallenexpensify commented on Sep 14, 2026

mallenexpensify commented on Sep 14, 2026

mountiny commented on Sep 17, 2026

mallenexpensify commented on Sep 17, 2026

Payment Summary

garrettmknight commented on Sep 24, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions