TRAGIKOMIX: 1/ neres, o tom vim. 2/ to je pro me novinka.

Pojdme prosim resit tyhle dev-related veci v GitHubu.

LUCIEN: PR je vytvoren - obsahuje upgrade flutteru a Fix na issue #300.

Ovsem narazil jsem na 2 problemy a bohuzel netusim jestli souvisi s tim upgradem. To bych rad kdybyste mohli pripadne testnout na verzi flutteru ktery pouzivate aktualne, pokud se nepletu tak 2.5.3. Ja si zprovoznim fvm a snad budu schopen lepe switchovat mezi verzemi.

1. Problem c.1 je kdyz nahodim appku do simulatoru a prepnu se mezi tabem "Sledovane" a "Historie", tak mi to vyblije exception viz nize. Nicmene opravdu se to deje jen pri tom prvnim prokliku mezi taby. Nasledne uz je to ok.
Vliv na aplikaci zrejme nema, protoze funguje pak bez problemu.
Jelikoz nejsem jeste tak zdatnej v kodu fyxu a zaroven flutter/dartu, tak uplne neni pro me easy to prodebugovat/identifikovat problem. Nicmene zkusim hledat a pripadne dat vedet.

flutter: ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
flutter: The following assertion was thrown while finalizing the widget tree:
flutter: A ScrollController was used after being disposed.
flutter: Once you have called dispose() on a ScrollController, it can no longer be used.
flutter:
flutter: When the exception was thrown, this was the stack:
flutter: #0 ChangeNotifier._debugAssertNotDisposed.
flutter: #1 ChangeNotifier._debugAssertNotDisposed
flutter: #2 ChangeNotifier.dispose
flutter: #3 ScrollController.dispose
flutter: #4 _PullToRefreshListState.dispose
flutter: #5 StatefulElement.unmount
flutter: #6 _InactiveElements._unmount
flutter: #7 _InactiveElements._unmount.
flutter: #8 SingleChildRenderObjectElement.visitChildren
flutter: #9 _InactiveElements._unmount
flutter: #10 _InactiveElements._unmount.
flutter: #11 SingleChildRenderObjectElement.visitChildren
flutter: #12 _InactiveElements._unmount
flutter: #13 _InactiveElements._unmount.
flutter: #14 ComponentElement.visitChildren
flutter: #15 _InactiveElements._unmount
flutter: #16 _InactiveElements._unmount.
flutter: #17 ComponentElement.visitChildren
flutter: #18 _InactiveElements._unmount
flutter: #19 _InactiveElements._unmount.
flutter: #20 ComponentElement.visitChildren
flutter: #21 _InactiveElements._unmount
flutter: #22 _InactiveElements._unmount.
flutter: #23 ComponentElement.visitChildren
flutter: #24 _InactiveElements._unmount
flutter: #25 ListIterable.forEach (dart:_internal/iterable.dart:39:13)
flutter: #26 _InactiveElements._unmountAll
flutter: #27 BuildOwner.lockState
flutter: #28 BuildOwner.finalizeTree
flutter: #29 WidgetsBinding.drawFrame
flutter: #30 RendererBinding._handlePersistentFrameCallback
flutter: #31 SchedulerBinding._invokeFrameCallback
flutter: #32 SchedulerBinding.handleDrawFrame
flutter: #33 SchedulerBinding._handleDrawFrame
flutter: #37 _invoke (dart:ui/hooks.dart:151:10)
flutter: #38 PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:308:5)
flutter: #39 _drawFrame (dart:ui/hooks.dart:115:31)
flutter: (elided 3 frames from dart:async)
flutter: ════════════════════════════════════════════════════════════════════════════════════════════════════

2. Problem c.2 je pouze u Androidu a jedna se o prvni inicializaci tokenu. Kdyz na slidu 2, kde se zobrazuje token, kliknu/double-kliknu na token, zobrazi skoro BSD I kdyz spise je to cervena obrazovka :)
Imgur: The magic of the Internet
https://imgur.com/a/pfkNitM
Zkusil jsem zbuildene apk hodit na muj zalozni android phone, tam sice neni ta red screena, ale i tak to zbledne/zbela a vypada to mrtve.

TRAGIKOMIX: Rovnou priznam, ze na nejaky sofistikovany testy jsem nikdy nemel moc casu. Neco malo sice je, ale zadna slava to neni. Obecne to delam tak, ze nez vyjde beta, testuju app u sebe na telefonu. Kdyz vse funguje jak ma, vydam betu. Jinymi slovy - udelej PR, Travis spusti testy, kdyz bude vse ok, otestuju, mergnu do developu a pak se uvidi :)

TRAGIKOMIX: Testu je tam par. Pusti se automaticky, kdyz udelas PR, nebo lokalne se daj pustit pres "flutter test". Mne teda lokalne jeden pada, vypada to na nejakej problem s timezonama, ale Travis s tim problem nema, tak jsem v tom nevrtal, jen jsem si ho lokalne zaignoroval

LUCIEN:
Issue #300 mam taky fixed. Udelam PR s tim upgradem ale rad bych tam asi prvne sjel nejak ty testy nebo pripadne udelal hlubis regresi.

TRAGIKOMIX: Simulator si credentials pamatuje, i napric ruznejma strojema a restartama... Nicmene je to samozrejme mozne pres env, podivej se na tohle https://pub.dev/packages/flutter_dotenv