Can not subscribe to observable again once the app is unsubscribed with FormValidationCombineLatestFragment about rxjava-android-samples

[marukami]

1. The onDestroy is not not guaranteed to be called So I generally put my unsubscribe calls is the onStop. For this example onPause is also fine.
2. It does recreate the subscription and the observable s. The issues is when you restart the fragment you lose the observable s and the new observable once again will skip the first event. So, you have to enter something in each field again before it will validate the fields.

[marukami]

Sorry you are also right in that _combineLatestEvents should be in onStart or onResume.

[tomoima525]

@marukami
Thank you for your reply.

1. My concern here is that after the validation is passed and the app goes background and comes to foreground, the "Submit" button is kept enabled even if I changed inputs to invalid entries. The screen below shows the issue.

The only way to avoid this issue was to call _combineLatestEvents() at onCreateView() and _subscription.unsubscribe() at onDestroy().
Calling _subscription.unsubscribe() at onStop() reproduced the issue as well. I was wondering if there is any other option to solve this.

new observable once again will skip the first event

Oh, I didn't know this function. I got your point. Thank you.

[marukami]

Instead of using skip you could use filter and prevent events from empty fields. So, that way when the fragment resumes form a valid state the Func3 is invoked, and editing any field will also invoke the Func3. I've made a fork you can see here CombineLastest with filter.

Only issue with doing it this way is you lose the invalid state when the field is empty. I'll work on dealing with that edge case after work.

[marukami]

So I added a skipWhile so it will now handle the empty field after editing use case. @kaushikgopal thoughts/suggestions on if this should be a PR?

[tomoima525]

@marukami great. This is a better solution. I would recommend this as a PR.

[kaushikgopal]

hey @tomoima525 : sorry for keeping this issue alive forever. over the course of the numerous changes, at some point, i changed the unsubscribing to happen onDestroyView. This in concert with onCreateView should do the trick.

if i'm missing something, feel free to chime in.

as always thanks @marukami for the insight on what was happening in the first place.