You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 23, 2020. It is now read-only.
I have a fragment hosted by an activity. Within the fragment, I create an RxLoader by:
RxLoader1<DealSavable, MyData> myLoader;
myLoader = RxLoaderManager.get(getActivity()).create(..., new RxLoaderObserver() { @OverRide
public void onNext(MyData value) {
}
...
});
myLoader.restart();
The problem is: If the loader retrieved some data, and after that, if the activity is re-created, during the above "create()" method call, the onNext() is called immediately with previously loaded stale data.
Is this a bug? How can I make sure that onNext() is called only when "restart()" is called?
I have a fragment hosted by an activity. Within the fragment, I create an RxLoader by:
RxLoader1<DealSavable, MyData> myLoader;
myLoader = RxLoaderManager.get(getActivity()).create(..., new RxLoaderObserver() {
@OverRide
public void onNext(MyData value) {
}
...
});
myLoader.restart();
The problem is: If the loader retrieved some data, and after that, if the activity is re-created, during the above "create()" method call, the onNext() is called immediately with previously loaded stale data.
Is this a bug? How can I make sure that onNext() is called only when "restart()" is called?