Model reference becomes null after adding to a different model relation

Summary

With the code below it can be seen that I have an Account : Program relation as well as Account : []Account. The Program can be accessed through the Account until a new relation is added, after that I the account.program is immediately null. Using stetho it can be seen that the program is now a null value.

Account

class Account {
    public Program program;
    public RealmList<Account> following;
}

Follow account

// ...
realm.executeTransaction(new Realm.Transaction() {
    @Override
    public void execute(Realm realm) {
        Account currentUser = realm.where(Account.class)
                .equalTo(Account.ATTR_KEY, Session.getAccountKey(context))
                .findFirst();

        Account a = resp.body();          // account's program is not null here
        Log.d("program", currentUser.program.name);   // shows the program name
        currentUser.following.add(a);   // results in Account -> Program disconnect
        Log.d("program", currentUser.program.name);   // null pointer exception
    }
});
// ...

Version of Realm and tooling

Realm version(s): 2.0.2

Android Studio version: ? 2.2.1

Which Android version and device: ? 4.2.1 Galaxy Nexus

[chrisolsen]

You are right in regards to the account payload from resp.body() not containing the program and then deleting it.

Performing a realm lookup for the account, then adding that account reference works.

Sorry for the post here, I thought it was a bug 😦

[Zhuinden]

Well considering you overrode the original currentUser as the proxy pointed to the same object, it’s no wonder the error looked so arcane 🙂