rx-java2

I'm using RxJava to iterate over a list of files, making a network call to upload each file, then collect the files that were successfully uploaded in a list and persist those files in the subscriber on success. This code works, except for when an error occurs. The behavior should be that it logs the error and continues, which it does, except when an error occurs the subscriber's onSuccess lambda never gets called. Is the observer expecting the same number of elements to be emitted as are in the original iterable? How can I skip the errors and have it complete once all items have been iterated

My question can be a duplicate of How to use CompositeDisposable of RxJava 2? But asking to clear one more doubt. According to the accepted answer // Using clear will clear all, but can accept new disposable disposables.clear(); // Using dispose will clear all and set isDisposed = true, so it will not accept any new disposable disposables.dispose(); In my case, I'm using fragments as my views (View layer in MVP) and in some scenarios, I add active fragment to backstack, which actually does not kill the Fragment but only its view. Which means only onDestroyView is called and not the onDestroy .

I need to perform a request, if my token is expired I need to refresh it and retry the request. This is how I'm trying to do it, at the moment I can refresh the token but it throws me a NetworkOnMainThreadException. It finishes the request,update the token and reaches logs, but that exception its killing me. How can I avoid that? public Observable<Estabelecimento> listarEstabelecimentos() { return Observable.defer(this::getListarEstabelecimentoObservable) .retryWhen(throwableObservable -> throwableObservable.flatMap( throwable -> { if (throwable instanceof UnauthorizedException) { return

So simply, the DAO @Query("DELETE FROM Things WHERE someIdOfTheThing IN (:listOfId)") abstract fun deleteThings(listOfId: MutableList<String>): Maybe<Int> usage, mDisposables.add(mThingsDao .deleteThings(listOfId) .subscribeOn(Schedulers.io()) .observeOn(AndroidSchedulers.mainThread()) .subscribe({ ... }, { ... }) ) and error, // Cannot access database on the main thread since it may potentially lock the UI for a long period of time. The simple idea i was thinking is to specify subscribeOn(Schedulers.io()) and then give all the job to Rx's magical hands, but failed. So what's the thing i'm

I open example code BasicRxJavaSample (from this article Room+RxJava ) The main thing is there: @Rule public InstantTaskExecutorRule instantTaskExecutorRule = new InstantTaskExecutorRule(); And BasicRxJavaSample is all ok. But I can not apply this in my test. That's what's going on: Cannot resolve symbol InstantTaskExecutorRule And manual import does not work: My autocompletion works like this But should be so My app build.gradle ( full gradle here ): // tests testImplementation 'junit:junit:4.12' androidTestCompile "com.android.support:support-annotations:$supportVersion" testImplementation

When using rxjava 1.x i used to return Observable<Void> to handle empty response from retrofit: @POST( "login" ) Observable<Void> getToken( @Header( "Authorization" ) String authorization, @Header( "username" ) String username, @Header( "password" ) String password ); But since rxjava 2.x won't emit anything with Void is there any good practice to handle those empty responses? Completable was designed for such cases. It available since RxJava 1.1.1. From the official docs: Represents a deferred computation without any value but only indication for completion or exception. The class follows a