Handle Intercom widget load failures without reporting an application error
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- authentication, frontend
Research direction
Start in src/components/Intercom/IntercomWidget.ts at line 85, where the widget script error handler rejects after a load failure. Trace how this optional widget is initialized during /auth/login and how errors reach Sentry. Done means a blocked or unavailable widget degrades gracefully without an unhandled application error or Sentry event, while authentication continues normally.
Written by the indexing model from the issue text.
Description
Description
The auth UI reports Failed to load the Intercom widget script to Sentry when the third-party widget cannot load. The issue has remained ongoing since 2026-07-16 and reached 978 events affecting 279 users as of 2026-09-18.
Evidence
- Sentry issue: https://decentraland.sentry.io/issues/7614585377/
- In-app frame:
src/components/Intercom/IntercomWidget.ts:85, where the script error handler rejects with this error. - The latest event was a production iOS browser session on
/auth/login; nearby network requests also failed, consistent with a client/network or content-blocking failure rather than an auth-flow exception.
Expected behavior
A failure to load the optional support widget must not produce an unhandled application error or Sentry event. It should degrade gracefully while preserving normal authentication behavior.
Reported by Sentry
Requested by Lautaro Petaccio (<@U025WCHLMN3>)
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 3
- Avg merge
- 8h 2m
- Merged PRs (30d)
- 38
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from decentraland/auth
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
decentraland/auth#490 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 68/100
decentraland/auth#516 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
decentraland/auth#514 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
decentraland/auth#448 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
decentraland/auth#447 ·
All issues in decentraland/auth
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100