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
[Due for payment 2026-08-31] [Sentry: APP-J2J] Web onboarding interested-features crash — baseHeadline DOM missing in modifyFeaturesStep #97100
TL;DR: This crash is not coming from App code. The frames modifyFeaturesStep and baseHeadline.innerText = COPY.base_headline reference symbols that don't exist anywhere in this repo (or its node_modules). It's an injected third-party script (browser extension / autofill / translation tool) throwing inside the page, which Sentry's global onunhandledrejection handler captures indiscriminately. The recommended fix is to filter it out in Sentry, not to change onboarding code.
What is the root cause of that problem?
The reported stack is foreign to App:
modifyFeaturesStep — no match anywhere in the repo (excluding/including node_modules).
baseHeadline / COPY.base_headline — no match. App has no global COPY object.
.innerText = ... — App is React Native Web; it renders through React and never mutates the DOM via .innerText. There are zero .innerText assignments in src/.
That combination (imperative .innerText DOM mutation + a global COPY object with snake_case keys + a bespoke modifyFeaturesStep routine) is characteristic of a script injected into the page from outside the bundle — a browser extension, autofill/password manager, or a translation/marketing snippet. The auto.browser.global_handlers.onunhandledrejection mechanism means Sentry's global handler swept up an unhandled promise rejection thrown by that script; Sentry attributes it to whatever route the tab was on (/onboarding/interested-features) even though App didn't throw it.
The impact profile is consistent with injected-script noise, not a real regression: very low unique users (20 + 7), single platform (Mobile Safari), single version.
What changes do you think we should make in order to solve the problem?
App-side, the fix is to stop ingesting foreign errors rather than to touch onboarding:
In src/setup/telemetry/setupSentry.ts:18-32 (which today only sets ignoreErrors: [CONST.ERROR.UPDATE_REQUIRED]), add Sentry's third-party error filter so events whose stack frames don't originate from Expensify bundles are dropped — either the thirdPartyErrorFilterIntegration (keyed via the bundler plugin applicationKey), or a beforeSend that discards events whose top in-app frame URL isn't an Expensify origin.
Mark the two Sentry issues (APP-J2J, APP-J1N) as ignored, or add a Sentry inbound data filter for these frames.
What alternative solutions did you explore? (Optional)
Verify the origin first (recommended before coding): the issue body only lists the top frames without their absolute file URLs. Open APP-J2J / APP-J1N and check the frame abs_path — it will almost certainly be a chrome-extension:// / moz-extension:// / safari-web-extension:// URL or a non-Expensify CDN, which confirms it's external and lets you scope the filter precisely.
Considered whether onboarding renders interested-features before a required node mounts — ruled out, because none of the crashing symbols exist in the onboarding code (src/pages/OnboardingInterestedFeatures/) or anywhere else in App.
Investigation details & confidence
Confidence: High that the crash is not in App code (exhaustive grep of repo + node_modules for all three symbols returns nothing, and App never uses .innerText). Medium on the precise external source, since the frame file URLs weren't included in the issue — confirm via the Sentry frames as noted above.
Checked against App@557846e:
grep -rn "modifyFeaturesStep" → no matches (repo + node_modules)
grep -rn "baseHeadline\|base_headline\|COPY\.base" → no matches
grep -rn "\.innerText" src/ → no matches
Quick scan for a pre-existing tracking issue found none.
Next Steps for Contributor+ team: To accept:@MelvinBot implement [this](https://github.com/Expensify/App/issues/97100) to create a draft PR adding the third-party error filter in setupSentry.ts. To refine:@MelvinBot <your feedback> To reject: Explain why you are rejecting Melvin's proposal.
changed the title [-][Sentry: APP-J2J] Web onboarding interested-features crash — baseHeadline DOM missing in modifyFeaturesStep[/-][+][Due for payment 2026-08-31] [Sentry: APP-J2J] Web onboarding interested-features crash — baseHeadline DOM missing in modifyFeaturesStep[/+]on Aug 31, 2026
Activity
melvin-bot commentedon Jul 27, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ChavdaSachin (
External)melvin-bot commentedon Jul 27, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022081739667212393404
MelvinBot commentedon Jul 27, 2026
Proposal
What is the root cause of that problem?
The reported stack is foreign to App:
modifyFeaturesStep— no match anywhere in the repo (excluding/includingnode_modules).baseHeadline/COPY.base_headline— no match. App has no globalCOPYobject..innerText = ...— App is React Native Web; it renders through React and never mutates the DOM via.innerText. There are zero.innerTextassignments insrc/.That combination (imperative
.innerTextDOM mutation + a globalCOPYobject withsnake_casekeys + a bespokemodifyFeaturesSteproutine) is characteristic of a script injected into the page from outside the bundle — a browser extension, autofill/password manager, or a translation/marketing snippet. Theauto.browser.global_handlers.onunhandledrejectionmechanism means Sentry's global handler swept up an unhandled promise rejection thrown by that script; Sentry attributes it to whatever route the tab was on (/onboarding/interested-features) even though App didn't throw it.The impact profile is consistent with injected-script noise, not a real regression: very low unique users (20 + 7), single platform (Mobile Safari), single version.
What changes do you think we should make in order to solve the problem?
App-side, the fix is to stop ingesting foreign errors rather than to touch onboarding:
src/setup/telemetry/setupSentry.ts:18-32(which today only setsignoreErrors: [CONST.ERROR.UPDATE_REQUIRED]), add Sentry's third-party error filter so events whose stack frames don't originate from Expensify bundles are dropped — either thethirdPartyErrorFilterIntegration(keyed via the bundler pluginapplicationKey), or abeforeSendthat discards events whose top in-app frame URL isn't an Expensify origin.What alternative solutions did you explore? (Optional)
abs_path— it will almost certainly be achrome-extension:///moz-extension:///safari-web-extension://URL or a non-Expensify CDN, which confirms it's external and lets you scope the filter precisely.interested-featuresbefore a required node mounts — ruled out, because none of the crashing symbols exist in the onboarding code (src/pages/OnboardingInterestedFeatures/) or anywhere else in App.Investigation details & confidence
Confidence: High that the crash is not in App code (exhaustive grep of repo +
node_modulesfor all three symbols returns nothing, and App never uses.innerText). Medium on the precise external source, since the frame file URLs weren't included in the issue — confirm via the Sentry frames as noted above.Checked against
App@557846e:grep -rn "modifyFeaturesStep"→ no matches (repo + node_modules)grep -rn "baseHeadline\|base_headline\|COPY\.base"→ no matchesgrep -rn "\.innerText" src/→ no matchesQuick scan for a pre-existing tracking issue found none.
Next Steps for Contributor+ team:
To accept:
@MelvinBot implement [this](https://github.com/Expensify/App/issues/97100)to create a draft PR adding the third-party error filter insetupSentry.ts.To refine:
@MelvinBot <your feedback>To reject: Explain why you are rejecting Melvin's proposal.
mountiny commentedon Jul 29, 2026
@ChavdaSachin can you review the Melvin bot proposal?
16 remaining items
mountiny commentedon Aug 18, 2026
@ChavdaSachin bump please
ChavdaSachin commentedon Aug 19, 2026
@mountiny I don't understand it fully.
It's better to find an expert to fix it.
Thank you.
Sorry for the delays 🙏
melvin-bot commentedon Aug 24, 2026
@mountiny @staszekscp @ChavdaSachin this issue is now 4 weeks old, please consider:
Thanks!
staszekscp commentedon Aug 31, 2026
Hey! This one's resolved, no errors since August 19th 🎉
[-][Sentry: APP-J2J] Web onboarding interested-features crash — baseHeadline DOM missing in modifyFeaturesStep[/-][+][Due for payment 2026-08-31] [Sentry: APP-J2J] Web onboarding interested-features crash — baseHeadline DOM missing in modifyFeaturesStep[/+]melvin-bot commentedon Aug 31, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)ChavdaSachin commentedon Aug 31, 2026
No payment needed here; ready to be closed.
cc. @mallenexpensify
melvin-bot commentedon Aug 31, 2026
Payment Summary
BugZero Checklist (@mallenexpensify)