Debugging with Sentry's Debug IDs

on YouTube ↗17m

" summary

Sentry Debug IDs create a one-to-one link between a minified JS bundle and its source map so error events stop pointing only to "main JS bundle." The talk shows using bun (auto-generates IDs), adding IDs with esbuild/webpack or Sentry CLI, and injecting a debug ID polyfill into runtime so the server can match errors. Example: a 100+ occurrence "API URL from undefined" stacktrace resolves to a specific file and line (line 63) after uploading maps and using the Expo plugin or Metro serializer patch.

AI-written summary · about

" chapters (10)

1. 0:00The problem with debugging
2. 1:08Source maps challenges
3. 2:18Introduction to debug IDs
4. 3:58Technical overview
5. 6:07Generating debug IDs
6. 8:43Runtime implementation
7. 9:46Sentry and React Native
8. 10:56Expo configuration
9. 12:45Metro configuration
10. 15:31Conclusion and Q&A

" related talks

• 17mDebugging should be easierCedric van Putten · App.js Conf 2023
• 28mThe Dark Art of BundlersMike Grabowski · Chain React 2017
• 23mCoding Mobile with the ProsGant Laborde · React Amsterdam 2017
• 18mWhat is your app actually doing in production?Kadi Kraman · App.js Conf 2026
• 28mDebugging and Beyond with ReactotronDarin Wilson · Chain React 2018
• 40mCrushing bugs with Redux architecture for iOSAlexey Demedetskiy · Mobile Fest 2018
• 29mBuilding Universal Windows Apps with React NativeRyan J. Salva · ReactiveConf 2016
• 08h 11mLive stream from Day 1James Ide, Evan Bacon, Kadi Kraman, Johannes Schickling, Fernando Rojo, Charlie Cheever, William Candillon, Nathan Wienert, Saad Najmi, Jon Samp, Kudo Chien, Krzysztof Piaskowy, Monica Restrepo, Marcin Skotniczny · App.js Conf 2023