OkBuck support

[paulononaka]

Goal

Build my app that uses Realm with OkBuck.

Expected Results

Build and runs normally as if I had built with Gradle.

Actual Results

The build and APK are successfully generated, but when I run the app an error is raised, forcing close the app. If I build the same dependencies with Gradle, not using OkBuck, it runs perfectly. Logcat:

E/AndroidRuntime( 3447): FATAL EXCEPTION: main
E/AndroidRuntime( 3447): Process: mobile.nonaka.com.nonakaapp.ci, PID: 3447
E/AndroidRuntime( 3447): java.lang.ExceptionInInitializerError: RealmTransformer doesn't seem to be applied. Please update the project configuration to use the Realm Gradle plugin. See https://realm.io/news/android-installation-change/
E/AndroidRuntime( 3447): 	at io.realm.RealmConfiguration.<clinit>(RealmConfiguration.java:77)
E/AndroidRuntime( 3447): 	at io.realm.RealmConfiguration$Builder.initializeBuilder(RealmConfiguration.java:428)
E/AndroidRuntime( 3447): 	at io.realm.RealmConfiguration$Builder.<init>(RealmConfiguration.java:391)
E/AndroidRuntime( 3447): 	at mobile.nonaka.com.nonakaapp.NONAKAApplication.onCreate(NONAKAApplication.java:44)
E/AndroidRuntime( 3447): 	at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1007)
E/AndroidRuntime( 3447): 	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4344)
E/AndroidRuntime( 3447): 	at android.app.ActivityThread.access$1500(ActivityThread.java:135)
E/AndroidRuntime( 3447): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1256)
E/AndroidRuntime( 3447): 	at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 3447): 	at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 3447): 	at android.app.ActivityThread.main(ActivityThread.java:5017)
E/AndroidRuntime( 3447): 	at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3447): 	at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 3447): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
E/AndroidRuntime( 3447): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
E/AndroidRuntime( 3447): 	at dalvik.system.NativeStart.main(Native Method)

https://realm.io/news/android-installation-change did not help.

Steps & Code to Reproduce

Build any app with Realm with OkBuck and run it.

Code Sample

NONAKAApplication.java line 44 has this code:

            RealmConfiguration realmConfiguration = new RealmConfiguration.Builder(this)
                    .schemaVersion(1)
                    .encryptionKey(realmKeyProvider.getRealmKey())
                    .deleteRealmIfMigrationNeeded()
                    .build();

This is my Gradle configuration that I used to generate the Buck files:

buildscript {
    repositories {
        jcenter()
    }
    dependencies {
        classpath "io.realm:realm-gradle-plugin:2.2.1"
    }
}

apply plugin: 'realm-android'

Version of Realm and tooling

Realm version(s): 2.2.1

Realm sync feature enabled: no

Android Studio version: 2.2.3

Which Android version and device: Any device
minSdkVersion 18
targetSdkVersion 25
compileSdkVersion 25
buildToolsVersion '25.0.2'

OkBuck: 0.13.1

Gradle: 3.2

Android Gradle Plugin: 2.2.3

Thanks a lot.

[Zhuinden]

That's because OkBuck doesn't support the Transform API yet.

[paulononaka]

@Zhuinden didn't notice that. Thanks a lot! Does anyone know though if it is possible to use Realm without this Transform API (maybe a older version of Realm)?

[Zhuinden]

The last Realm that does not use the Realm-Transformer and the Transform API is compile "io.realm:realm-android:0.87.5"

In that version of Realm, RealmObjects cannot have custom methods, and custom logic in getters/setters.

Also, RealmResults are live in transactions, so you need to reverse iterate them instead of using for(Blah blah: blahs).

[paulononaka]

@Zhuinden thanks man. It helped me a lot!

[kageiit]

Transform api support is actually available in okbuck, but it is not documented yet. It's a bit of work to setup right now, so we are working to make it more plug and play and will document it fully at that point.

[cmelchior]

Thanks for the info @kageiit 👍

[meierjan]

Just for future reference:
uber/okbuck#305

[kageiit]

Question for Realm maintainers. The way transforms work in buck is that they do not have access to the gradle project model as they are run like commandline applications. This would require the RealTransformer to provide an alternate constructor that can accept a config file as an input for various configuration options instead of relying on the gradle plugin extension. Would like your thoughts on the matter

[cmelchior]

Given the above, and that support for Transformers have been merged in OkBuck I'm re-opening this as a feature request for adding support for OkBuck. We would have to look more closely at how specifically the config file looks like, but just browsing our RealmTransformer we only use two things from the Gradle project:

1. We have a custom realm closure with a setting syncEnabled. I don't know how OkBuck handles custom configuration closures, but we would have to migrate that anyway.

2. We access project.android.bootClasspath to acquire a reference to the android.jar. This would have to be provided by Buck somehow I think.

@zaki50 Do you have any input to this?