orientation change messes it up about rxjava-android-samples HOT 2 CLOSED

One of the advantages​ of​ RxJava​ usage​ in Android is​ it helps us avoid​ having to​ dealing with loaders.​ No loaders for me thank you :)​

​
Retained fragments I could do​, but the reason i haven't already is because ​the objective​ of these examples ​is to demonstrate RxJava usage as clearly as possible. Adding the retained fragment implementation is supplementary and can be tacked on once ​the ​ RxJava usage is understood. If i do add retained fragments, then a ​large part of the code in the examples will point to non-RxJava boilerplate implementation and that defeats the original purpose. But your point is well taken, if I did need to retain state across orientation changes, I would probably use a retained fragment to achieve it.

Handled erros in the logcat are fine. ​If ​ the orientation change crashes ​the app ​ like a previous issue ​led me to then that most definitely calls for a fix/change.​ Which example were you specifically pointing to?

from rxjava-android-samples.

closing this one. feel free to reopen if you want to explore this issue more.

from rxjava-android-samples.