maltemedocs

Wouldn't it already help here to drop the Material Widget from the SettingsContainer Widget? That way the color behind the widget should be applied. At that seems to work for...

@PaulanerAlex I can confirm this. I'm currently double checking that it is not an initialization error, that the output fits. But so far I see this: The same algorithm parameters...

@yulkin2002 If it's inconsistently and only on first pass when you re-open the section, try converting `MyNameLoginView` and/or `HomeScreen` to a StatefulWidget. That helped me in a similar scenario when...

@yulkin2002 I continue to use them. Literally the only change was converting the widget from Stateless to Stateful. That alone prevented Flutter from re-using the old controller on a first...

Just got bit by this. Completely ported an internal http API class to use `http` top level function, as it feels cleaner than the client solution and I'm not interested...

Just to offer a workaround: `Get.isLogEnable = false;` seemed to work for me (not using a `GetMaterialApp` though).

@matthewkooshad I had placed it early. The app had a main -> runZonedGuarded -> runApp flow. I did put the `Get.isLogEnable = false;` into the runZonedGuarded function, a bit before...

@terrier989 I can confirm that it is a lot better now. I'm not sure where I tested the 100k iterations before that took 40 seconds, but according to old documentation...

This is an especially bad ticket for a stale bot to mark. How about disabling the stale bot? It is harmful to projects anyway.