All Versions
169
Latest Version
Avg Release Cycle
35 days
Latest Release
576 days ago

Changelog History
Page 6

  • v5.15.1 Changes

    September 09, 2019

    ✨ Enhancements

    • None.

    🛠 Fixed

    • 🏗 Projects with flatDirs repositories defined crashed the build with MissingPropertyException. (Issue #6610, since 5.15.0).

    Compatibility

    • Realm Object Server: 3.21.0 or later.
    • ⬆️ File format: Generates Realms with format v9 (Reads and upgrades all previous formats)
    • 🚀 APIs are backwards compatible with all previous release of realm-java in the 5.x.y series.

    Internal

    • None.

  • v5.15.0 Changes

    September 05, 2019

    ✨ Enhancements

    • 🏗 [ObjectServer] Added support for Client Resync for fully synchronized Realms which automatically will recover the local Realm in case the server is rolled back. This largely replaces the Client Reset mechanism. Can be configured using SyncConfiguration.Builder.clientResyncMode(). (Issue #6487)

    🛠 Fixed

    • ⬆️ Huawei devices reporting Permission denied when opening a Realm file after an app upgrade or factory reset. This does not automatically fix already existing Realm files. See this FAQ entry for more details. (Issue #5715)
    • ⚡️ Realm.copyToRealm() and Realm.insertOrUpdate() crashed on model classes if @LinkingObjects was used to target a field with a re-defined internal name in the parent class (e.g. by using @RealmField). (Issue #6581)

    Compatibility

    • Realm Object Server: 3.21.0 or later.
    • ⬆️ File format: Generates Realms with format v9 (Reads and upgrades all previous formats)
    • 🚀 APIs are backwards compatible with all previous release of realm-java in the 5.x.y series.

    Internal

    • 🔀 Implemented direct access to sync workers on Cloud, bypassing the Sync Proxy: the binding will override the sync session's url prefix if the token refresh response for a realm contains a sync worker path field.
    • ⚡️ Updated to Object Store commit: 9f19d79fde248ba37cef0bd52fe64984f9d71be0.
    • ⚡️ Updated to Realm Sync 4.7.4.
    • ⚡️ Updated to Realm Core 5.23.2.

  • v5.14.1 Changes

    ✨ Enhancements

    • None.

    🛠 Fixed

    • ⚡️ Realm.copyToRealm() and Realm.insertOrUpdate() crashed on model classes if @LinkingObjects was used to target a field with a re-defined internal name in the parent class (e.g. by using @RealmField). (Issue #6581)

    Compatibility

    • Realm Object Server: 3.21.0 or later.
    • ⬆️ File format: Generates Realms with format v9 (Reads and upgrades all previous formats)
    • 🚀 APIs are backwards compatible with all previous release of realm-java in the 5.x.y series.

    Internal

    • None.

  • v5.14.0 Changes

    August 12, 2019

    🗄 Deprecated

    • 🔀 [ObjectServer] SyncCredentials.nickname() has been deprecated in favour of SyncCredentials.usernamePassword().
    • 🔀 [ObjectServer] SyncCredentials.IdentityProvider.NICKNAME has been deprecated in favour of SyncCredentials.IdentityProvider.USERNAME_PASSWORD.

    ✨ Enhancements

    • None.

    🛠 Fixed

    • None.

    Compatibility

    • Realm Object Server: 3.21.0 or later.
    • ⬆️ File format: Generates Realms with format v9 (Reads and upgrades all previous formats)
    • 🚀 APIs are backwards compatible with all previous release of realm-java in the 5.x.y series.

    Internal

    • None.

  • v5.13.1 Changes

    August 05, 2019

    🗄 Deprecated

    • 🔀 SyncCredentials.nickname() has been deprecated in favour of SyncCredentials.usernamePassword().
    • 🔀 SyncCredentials.IdentityProvider.NICKNAME has been deprecated in favour of SyncCredentials.IdentityProvider.USERNAME_PASSWORD.

    ✨ Enhancements

    • None.

    🛠 Fixed

    • [ObjectServer] The C++ networking layer now correctly uses any system defined proxy the same way the Java networking layer does. (Issue #6574).
    • 🔌 The Realm bytecode transformer now works correctly with Android Gradle Plugin 3.6.0-alpha01 and beyond. (Issue #6531).
    • Queries on RealmLists with objects containing indexed integers could return the wrong result. (Issue #6522, since 5.11.0)

    Compatibility

    • Realm Object Server: 3.21.0 or later.
    • ⬆️ File format: Generates Realms with format v9 (Reads and upgrades all previous formats)
    • 🚀 APIs are backwards compatible with all previous release of realm-java in the 5.x.y series.

    Internal

    • ⚡️ Updated JavaAssist in the Realm Transformer to 3.25.0-GA.
    • ⚡️ Updated to Realm Core 5.23.1.
    • ⚡️ Updated to Realm Sync 4.7.1.
    • ⚡️ Updated to Object Store commit: bcc6a7524e52071bfcd35cf740f506e0cc6a595e

  • v5.13.0 Changes

    July 23, 2019

    ✨ Enhancements

    • 🔀 [ObjectServer] Added support for faster initial synchronization for fully synchronized Realms. (Issue #6469)
    • [ObjectServer] Improved session lifecycle debug output. (Issue #6552).

    🛠 Fixed

    • None.

    Compatibility

    • Realm Object Server: 3.21.0 or later.
    • ⬆️ File format: Generates Realms with format v9 (Reads and upgrades all previous formats)
    • 🚀 APIs are backwards compatible with all previous release of realm-java in the 5.x.y series.

    Internal

    • ⚡️ Updated to Realm Core 5.22.0.
    • ⚡️ Updated to Realm Sync 4.6.1.
    • ⚡️ Updated to Object Store commit f0d75261fc8d332c20dc82f643dd795c0f4c7aec

  • v5.12.0 Changes

    June 20, 2019

    ✨ Enhancements

    • 🔀 [ObjectServer] Added SyncManager.refreshConnections() that can be used to manually trigger a reconnect for all sessions. This is useful if the device has been offline for a long time or fail to detect that it regained connectivity. (Issue #259)
    • ➕ Added RealmResults.asJson() in @Beta that returns the result of the query as a JSON payload (#6540).

    🛠 Fixed

    • [ObjectServer] PermissionManager stopped working if an intermittent network error was reported. (Issue #6492, since 3.7.0)
    • The Kotlin extensions library no longer defines a app_name, which in some cases conflicted with the app_name defined by applications. (Issue #6536, since 4.3.0)

    Compatibility

    • Realm Object Server: 3.21.0 or later.
    • ⬆️ File format: Generates Realms with format v9 (Reads and upgrades all previous formats)
    • 🚀 APIs are backwards compatible with all previous release of realm-java in the 5.x.y series.

    Internal

    • ⚡️ Updated to Realm Core 5.22.0.
    • ⚡️ Updated to Realm Sync 4.6.1.
    • ⚡️ Updated to Object Store commit 7c3ff8235579550a3e3c6060c47140b2005174f5

  • v5.11.0 Changes

    May 01, 2019

    NOTE: This version is only compatible with Realm Object Server 3.21.0 or later.

    ✨ Enhancements

    • 0️⃣ [ObjectServer] Added RealmQuery.includeLinkingObjects(). This is only relevant for Query-based Realms and tells subscriptions to include objects linked through @LinkingObjects fields as part of the subscription as well. Objects referenced through objects and lists are always included as a default. (Issue #6426)
    • 🐎 Encryption now uses hardware optimized functions, which significantly improves the performance of encrypted Realms. (Realm Core PR #3241)
    • 👌 Improved query performance when using RealmQuery.in() queries. (Realm Core PR #3250).
    • 👌 Improved query performance when querying Integer fields with indexes, e.g. primary key fields. (Realm Core PR #3272).
    • 👌 Improved write performance when writing changes to disk (Realm Core PR #2927)
    • ➕ Added support for incremental annotation processing added in Gradle 4.7. (Issue #5906).

    🛠 Fixed

    • [ObjectServer] Fix an error in the calculation of the downloadableBytes value sent by ProgressListeners.
    • 🔀 [ObjectServer] HTTP requests made by the Sync client now always include a Host: header, as required by HTTP/1.1, although its value will be empty if no value is specified by the application.
    • [ObjectServer] The server no longer rejects subscriptions based on queries with distinct and/or limit clauses.
    • ⚡️ [ObjectServer] If a user had canCreate but not canUpdate privileges on a class, the user would be able to create the object, but not actually set any meaningful values on that object, despite the rule that objects created within the same transaction can always be modified.
    • ⚡️ Native crash happening if bulk updating a field in a RealmResult would cause the object to no longer be part of the query result. (Issue #6478, since 5.8.0).

    Compatibility

    • Realm Object Server: 3.21.0 or later.
    • ⬆️ File format: Generates Realms with format v9 (Reads and upgrades all previous formats)
    • 🚀 APIs are backwards compatible with all previous release of realm-java in the 5.x.y series.

    Internal

    • ⚡️ Updated to Realm Core 5.19.1.
    • ⚡️ Updated to Relm Sync 4.4.2.
    • ⚡️ Updated to Object Store commit e4b1314d21b521fd604af7f1aacf3ca94272c19a

  • v5.10.0 Changes

    March 22, 2019

    ✨ Enhancements

    • ⚡️ [ObjectServer] Added 4 new fields to query-based Subscriptions: createdAt, updatedAt, expiresAt and timeToLive. These make it possible to better reason about and control current subscriptions. (Issue #6453)
    • ⚡️ [ObjectServer] Added the option of updating the query controlled by a Subscription using either RealmQuery.findAllAsync(String name, boolean update), RealmQuery.subscribe(String name, boolean update) or Subscription.setQuery(RealmQuery query). (Issue #6453)
    • [ObjectServer] Added the option of setting a time-to-live for subscriptions. Setting this will automatically delete the subscription after the provided TTL has expired and the subscription hasn't been used. (Issue #6453)

    🛠 Fixed

    • Dates returned from the Realm file no longer overflow or underflow if they exceed Long.MAX_VALUE or Long.MIN_VALUE but instead clamp to their respective value. (Issue #2722)

    Compatibility

    • Realm Object Server: 3.11.0 or later.
    • ⬆️ File format: Generates Realms with format v9 (Reads and upgrades all previous formats).
    • 🚀 APIs are backwards compatible with all previous release of realm-java in the 5.x.y series.

    Internal

    • ⚡️ Updated to Object Store commit: e9819ed9c77ed87b5d7bed416a76cd5bcf255802

  • v5.9.1 Changes

    February 21, 2019

    ✨ Enhancements

    • None

    🛠 Fixed

    • [ObjectServer] Reporting too many errors from the native layer resulted in a native crash with local reference table overflow. (Issue #249, since 5.9.0)

    Compatibility

    • Realm Object Server: 3.11.0 or later.
    • ⬆️ File format: Generates Realms with format v9 (Reads and upgrades all previous formats)
    • 🚀 APIs are backwards compatible with all previous release of realm-java in the 5.x.y series.

    Internal

    • None