Member-only story
Flutter Frankenstein Broken Error Techniques
Do you know what that means? Tired of getting errors and fully deleting the Flutter project and starting over? There is a better way. Let me show you how.
Background
The reason I call it Frankenstein is that we have a framework that is dissimilar in its approaches to specific things. For example, in platform targeting, we have two different color systems to deal with native differences. So to deal with all those dissimilar moving parts, it does pay dividends to get some best practices in place so that when you receive and error report like this:
You immediately know either its cause or you know how to track down its cause. And on purpose I have shown a hard error to track down as the errors points to no specific app code lines.
In order to immediately know where to track it down, we have to have some best practices in place to correct error data about our Flutter app. That comes in some parts such as logging, build variants, Dart Zones, and application error catching.
Let’s see how to set it up.
