Poor behavior of Realm with transient keyword

[AntonAndreevEpam]

Goal

I am having few cases where I needed to exclude fields from Gson serialization, but I need them in my Realm database.

Expected Results

Previously I used transient keyword for such cases and it worked fine.

Actual Results

Right now I'm having java.lang.IllegalArgumentException: Field does not exist exception when trying to do a query by using field marked as transient.

I found out that this is happening because of behavior implemented in this issue #4279

Fields marked as transient are ignored even if I put @Required on them.

Version of Realm and tooling

Realm version(s): 5.0.0

[Zhuinden]

Transient fields are implicitly ignored since 3.2.0 and it's perfectly fine that way (#4279).

Previously you had to use @Ignore for them even though you generally shouldn't want to save transient fields to Realm.

I am having few cases where I needed to exclude fields from Gson serialization, but I need them in my Realm database.

Then use @Expose and enable the usage of the expose annotation with GsonBuilder

And mark the JSON fields with @Expose that you want to serialize

---

From code quality standpoint, you're getting this issue because you re-use Realm schema definition as API response, even though they are two very separate things.

[AntonAndreevEpam]

Hmm, somehow I missed @Expose annotation and used excludeFieldsWithModifiers(Modifier.TRANSIENT) instead.
Thank you for enlighten me.