> That code won't crazy because it's synchronou...

# rx

[dimsuz]

That code won't crazy because it's synchronous and triggering an error disposes the upstream so you'll never get 2 or 3 flowing down the stream

hah, but that was an example of layout, it actually operates on io() scheduler and is observed on android's main thread, I just didn't include this in the example (my bad). In place of Single.fromCallable() I actually have a retrofit service call which returns Single<SomeResponse> (but throws ConnectException when there is no internet.

So would you say that using concatMap here is a correct solution? I ended up with it, but still I don't think that having flatMap there should crash the app...