Svetlozar Kostadinov

Hey guys, @jhowens89 I've just seen your invite to come over here. Yes, nesting is one of the hardest problems I've faced. I've got 2 screens with nesting. They are...

Check out my fork: https://github.com/sevar83/conductor-dagger You'll have to import 2 additional artifacts with JitPack: ``` compile 'com.github.sevar83.conductor-dagger:annotation:2.1.4' annotationProcessor 'com.github.sevar83.conductor-dagger:processor:2.1.4' ``` If you use kotlin you should replace `annotationProcessor` with `kapt`...

I think I've got a race condition because of the `apply()`. My theory is that when another observer subscribes before the data is actually updated within `apply()` then the observer...

I derived my local RxJava1 tmdb service and just using the entities. I guess we need 1 main (entities + Call) and 2 additional optional artifacts - RxJava and RxJava2....

I've pushed a fork with support for Kotlin and RxJava2. But it's built as an Android Gradle library not a pure Java artifact. https://github.com/sevar83/tmdb-rxjava2-kotlin

Hi, do you have any idea whether porting the latest version for Android is doable at least theoretically? p.s. Oh, it's GPL. I guess that's a showstopper. Nevermind.

For future readers: I've fixed it by adding `APP_DEPRECATED_HEADERS := true` to Application.mk. Not the best solution but _works for now_ ™.

I think the local jitpack defines ndk.dir and your project defines ndkVersion and they different which causes the conflict. I don't know how to deal with this. The ndkVersion property...

The JitPack containers or VMs or whatever were instantiated with a fixed NDK version. At least that's how it was back in few years ago when I was dealing with...