In release mode crashed widgets should not show stacktrace and red background

[mehmetf]

Users do not understand what stacktraces mean and red color is too scary for them. It would be great to replace this (only in release mode) with a "broken widget" (may be something like aw, snap! page on Chrome?).

[Hixie]

Seems reasonable.

[gspencergoog]

It would probably be even more acceptable if users could perform an action, like submit feedback, from the "broken widget" screen.

[mehmetf]

@gspencergoog that might not be possible. The broken widget might manifest as a very small area on screen or not be visible at all.

I think the best way is for the app to install an error handler and do something from there. File feedback, show dialog, etc.

[tvolkert]

See also: #11206

[emesx]

Having control over what happens is necessary - I'd like my app to simply close (or do whatever native apps do). Maybe just assume that if FlutterError.onError is custom, then the programmer is in control and responsible?

[tvolkert]

@emesx that's #11206

[eseidelGoogle]

customer: six is reporting that even though they are handling errors in FlutterError and crashing they still see a red screen of death for a second before crashing. They would like to be able to display something other than the red screen of death during that time.