Sentry
Same ReferenceError, same function, different routes. Sentry split them by route.
Impact (snapshot at filing)
- Users (last 7d): 4 across both groups
- Users (total since first seen): 4
- Events: 43
- First seen: 2026-08-06
- Last seen: 2026-08-06
- Platform: web (Chrome)
- App version(s): 9.4.51-0
- Environment: production
- Affected route(s) (parameterized):
/r/:reportID/:reportActionID, /create/split-expense/overview/:reportID/:transactionID/...
- Mechanism:
auto.browser.browserapierrors.requestAnimationFrame
- Substatus: escalating
Stack trace (top frames)
app:///7572-<hash>.bundle.js:1:142600
app:///7572-<hash>.bundle.js:1:117469 (updateSplitTransactions)
The bundle is minified, but the enclosing function name survives: updateSplitTransactions.
Suspected cause
getAllReportActions is called inside updateSplitTransactions but is not in scope there — a missing or dropped import. This is a plain ReferenceError, so the call site fails every time it is reached; it is not a data-dependent edge case.
The call runs inside a requestAnimationFrame callback, which is why it escapes as an unhandled error rather than surfacing in a promise chain.
Grep the split expense update path for getAllReportActions and confirm it is imported in the module that defines updateSplitTransactions.
Reproduction
Open a split expense and trigger the update path that calls updateSplitTransactions. Because the symbol is simply undefined, any user reaching that line hits the crash.
Related
Upwork Automation - Do Not Edit
Sentry
Same
ReferenceError, same function, different routes. Sentry split them by route.Impact (snapshot at filing)
/r/:reportID/:reportActionID,/create/split-expense/overview/:reportID/:transactionID/...auto.browser.browserapierrors.requestAnimationFrameStack trace (top frames)
The bundle is minified, but the enclosing function name survives:
updateSplitTransactions.Suspected cause
getAllReportActionsis called insideupdateSplitTransactionsbut is not in scope there — a missing or dropped import. This is a plainReferenceError, so the call site fails every time it is reached; it is not a data-dependent edge case.The call runs inside a
requestAnimationFramecallback, which is why it escapes as an unhandled error rather than surfacing in a promise chain.Grep the split expense update path for
getAllReportActionsand confirm it is imported in the module that definesupdateSplitTransactions.Reproduction
Open a split expense and trigger the update path that calls
updateSplitTransactions. Because the symbol is simply undefined, any user reaching that line hits the crash.Related
Upwork Automation - Do Not Edit