rx-java2

Hi I'm new with RxJava and Kotlin and I loose some concepts about it. I have "api" like this: interface VehiclesService { @GET("/vehicles/") fun getVehicles(): Single<List<Vehicle>> } Then I create the retrofit client, etc.. like this: var retrofit = RetrofitClient().getInstance() vehiclesAPI = retrofit!!.create(VehiclesService ::class.java) finally I do the call: private fun fetchData() { compositeDisposable.add(vehiclesAPI .getVehicles() .subscribeOn(Schedulers.io()) .observeOn(AndroidSchedulers.mainThread()) .subscribe { vehicles -> displayData(vehicles) } ) } And here is where I have the

I just switched my code from asynctask to rxjava2 and I'm randomly getting this exception on my nexus: Camera is being used after Camera.release() was called in Galaxy s6 Edge Following is my code- Class Camera : public class Cameras { private static final String TAG = Cameras.class.getSimpleName(); private static final String SP_CAMERA_ID = "camera_id"; private static final int NO_NEXT_TASK = 0; private static final int NEXT_TASK_RELEASE_COMPLETE = 1; private static final int NEXT_TASK_SWITCH_COMPLETE = 2; private static final int NEXT_TASK_START_PREVIEW = 3; private Camera camera; private

In room the @Delete annotation doesn't emit anything. This is what the dao looks like @Dao public interface UserDao { @Delete void deleteUser(User user); //We can't use Maybe or Single or anything here } This makes it a problem while doing something like userRepository.deleteUser().subscribeOn since we have no emission coming the dao . I use the following code to call deleteUser on a background thread. Observable.just(appDatabase). subscribeOn(SchedulerProvider.getInstance().computation()). subscribe(db -> { userRepository.logoutUser(loggedUser.getLoggedInUser()); loggedUser.setLoggedInUser

I am currently choosing between RxJava 1.x or 2.x for my current project. I basically need a PublishSubject with a backpressure strategy onBackpressureLatest() . I want to choose RxJava 2.x, but i can't quite get my head around on how to apply a backpressure strategy to a PublishSubject , as it inherits from Observable and not from Flowable . Could you please tell me how to create a PublishSubject with a onBackpressureLatest() backpressure strategy in RxJava 2.x ? In 2.x the backpressure was moved to the base type Flowable and its hot partners PublishProcessor, ReplayProcessor etc.

I am trying to filter the list on the basis of it's property. For example, Sensors class has a property isActive and I want to get all the objects with isActive as true but I am unable to do it. I tried different ways but I didn't find the solution. Can someone help me to do it? Here is my code: mCompositeDisposable.add( fcService.getStationList() .subscribeOn(Schedulers.io()) .flatMap( stations -> { return fcService.getSensorList(stations.get(0).getName().getOriginal()); }) .subscribe(this::handleSensors, this::handleError) ); First, you need to emit each item from the List individually. That

PagedList<Object> is used for Android's cool paging library. To make the question as minimal as possible : If i have a list of strings like List<String> stringList; // it consists of 200 strings I want to convert stringList to type PagedList<String> like PagedList<String> pagedStringList; And also if i have a PagedList<Object> how can convert it to a List<Object> ? I went through this for reference If i try the other way round .... How can I convert List<Object> into DataSource.Factory<Integer, Object> ..so that indirectly i can convert it into PagedList<> ? From DataSource.Factory<Integer,

In RxJava1 flatmap had a overloaded method that allowed you to retain source values and pass it down the stream. I've gained this knowledge from the following blog post https://medium.com/rxjava-tidbits/rxjava-tidbits-1-use-flatmap-and-retain-original-source-value-4ec6a2de52d4 However, moving to RxJava2, I cannot seem to find it. I checked the changes from Rx1 and Rx2 and it is not listed. I would like to know if it exists still but I am perhaps not looking in the right place. I am using a Single by the way. I don't think Single ever supported this operator and the Observable / Flowable