Fearless Flutter Debugging: When All Else Fails, Hack the Tools!
summary
Shows how to edit the flutter_tools package in a local SDK, add print diagnostics, then force a rebuild by deleting flutter_tools.snapshot and flutter_tools.stamp so changes run. Demonstrates printing assembled dart-defines to reveal file-first then CLI-overrides precedence, adds extra_gen_snapshot_options to emit a JSON safe-obfuscation map for symbolizing obfuscated crash messages, and detects a missing Android plugin in profile/release builds that explains why a test plugin stopped running.
AI-written summary · about
chapters (9)
- 0:00Flutter tools hacking intro
- 1:05Why debugging isn't always enough
- 3:55Flutter Tools overview
- 7:50Modifying Flutter Tools
- 11:46Hacked tools use cases
- 16:26Obfuscation maps in prod
- 18:11Patrol plugin debugging
- 21:23Tools for learning/contrib
- 22:46Closing thoughts
related talks
33mLet's shake the Flutter tree
40mThread by Thread: The Hidden Battle for Flutter Stability
46mHow I Stopped Being Afraid and Learned to Love the Dart Compiler
02mDebug and profile your app with Flutter DevTools
38mDebugging performance issues with the Flutter DevTools
36mcontribute to the Flutter ecosystem.
32mcode generation productivity for Dart and Flutter
40mRevving up your Flutter IDE