Android - Realm does not work in a project with more than one module

Goal

• I have 2 modules where realm is located. One handles the database generic and another the database of the actually application. However When I try to add a RealmObject to the @RealmModule class it keeps telling me the RealmObject is not an object. However, if I change the location of the class to the application database module it actually works…

Exception trying to compile is the following:

e: error: RealmOne could not be added to the module. Only classes extending RealmObject or implementing RealmModel, which are part of this project, can be added.

Steps & Code to Reproduce

Application Module

• UserRealmModule

@RealmModule(classes = [RealmOne::class, RealTwo::class], library = true)
class UserRealmModule

Generic Database Module

• RealmOne

open class RealmOne(
    @Required
    @PrimaryKey
    @RealmField(REALM_ONE_ID)
    var id: String = ""
) : RealmObject() 

• RealmTwo

open class RealmTwo(
    @Required
    @PrimaryKey
    @RealmField(REALM_TWO_ID)
    var id: String = ""
) : RealmObject() 

Version of Realm and tooling

Realm version(s): {{io.realm:realm-gradle-plugin:5.8.0 }}

Android Studio version: 3.5.2

Android Build Tools version: 28.0.3

Gradle version: com.android.tools.build:gradle:3.5.1

[cmelchior]

@luispereira Why not just expose a module from the generic database module and combine them when opening the Realm?

 RealmConfiguration.Builder()
            .name(storageName)
            .schemaVersion(REALM_CURRENT_VERSION)
            .migration(realmMigrate)
            .modules(GenericModule(), UserModule())
            .deleteRealmIfMigrationNeeded()

[luispereira]

Yes @Zhuinden, but wouldn’t that impact only runtime? I’m having an issue in compile time

 RealmConfiguration.Builder()
            .name(storageName)
            .schemaVersion(REALM_CURRENT_VERSION)
            .migration(realmMigrate)
            .modules(UserRealmModule())
            .deleteRealmIfMigrationNeeded()