Commit e5c60fa
committed
fix(tracing): Fire ExpoRouterErrorBoundary marker at wrap-call time
The wrapped boundary only mounts when Expo Router actually
renders it (i.e., on an error), so a `useEffect`-based marker
would undercount adoption for apps that ship the wrap but never
hit a route error. Registering at wrap-call time fires as soon
as the user's route file evaluates.
No client is present if the wrap is called before
`Sentry.init()`, but that is very rare in practice — Expo Router
lazy-loads route files during navigation, so init has typically
completed by then.1 parent e9b715e commit e5c60fa
2 files changed
Lines changed: 9 additions & 7 deletions
File tree
- packages/core
- src/js/tracing
- test/tracing
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
67 | 67 | | |
68 | 68 | | |
69 | 69 | | |
70 | | - | |
71 | | - | |
72 | | - | |
73 | | - | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
74 | 76 | | |
| 77 | + | |
75 | 78 | | |
76 | 79 | | |
77 | 80 | | |
| |||
Lines changed: 2 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
89 | 89 | | |
90 | 90 | | |
91 | 91 | | |
92 | | - | |
93 | | - | |
94 | | - | |
| 92 | + | |
| 93 | + | |
95 | 94 | | |
96 | 95 | | |
97 | 96 | | |
| |||
0 commit comments