All Versions
137
Latest Version
Avg Release Cycle
22 days
Latest Release
100 days ago

Changelog History
Page 1

  • v10.0.0-BETA.5

    June 19, 2020
  • v10.0.0-BETA.4

    June 11, 2020
  • v10.0.0-BETA.3

    June 09, 2020
  • v10.0.0-BETA.2

    June 08, 2020
  • v10.0.0-BETA.1

    June 05, 2020
  • v10.0.0-ALPHA.1

    May 11, 2020
  • v7.0.6

    September 18, 2020

    ✨ Enhancements

    • 👍 Better exception messaging for UTF encoding errors. (Issue #7093)

    🛠 Fixes

    • 🛠 Fixes concurrent modification exceptions in the schema when refreshing a Realm (Issue #6876)
    • 👍 If you use encryption your application cound crash with a message like "Opening Realm files of format version 0 is not supported by this version of Realm". (#6889 among others, since v7.0.0)

    Compatibility

    • Realm Object Server: 3.23.1 or later.
    • Realm Studio: 5.0.0 or later.
    • ⬆️ File format: Generates Realms with format v11 (Reads and upgrades all previous formats from Realm Java 2.0 and later).
    • 🚀 APIs are backwards compatible with all previous release of realm-java in the 7.x.y series.

    Internal

    • ⬆️ Upgraded to Object Store commit: e29b5515df8b8adfe2454424b78878bb63879307.
    • ⬆️ Upgraded to Realm Sync: 5.0.23.
    • ⬆️ Upgraded to Realm Core: 6.0.26.
  • v7.0.5

    September 09, 2020

    ✨ Enhancements

    • None.

    🛠 Fixes

    • ⚡️ If you have a Realm file growing towards 2Gb and have a model class with more than 16 properties, then you may get a "Key not found" exception when updating an object. (Realm JS issue #3194, since v7.0.0)
    • In cases where you have more than 32 properties in a model class, you may get a currrupted file resulting in various crashes (Issue #7057, since v7.0.0)

    Compatibility

    • Realm Object Server: 3.23.1 or later.
    • Realm Studio: 5.0.0 or later.
    • ⬆️ File format: Generates Realms with format v11 (Reads and upgrades all previous formats from Realm Java 2.0 and later).
    • 🚀 APIs are backwards compatible with all previous release of realm-java in the 7.x.y series.

    Internal

    • ⬆️ Upgraded to Realm Sync: 5.0.22.
    • ⬆️ Upgraded to Realm Core: 6.0.25.
  • v7.0.4

    September 08, 2020

    ⬇️ Note: Fileformat has been bumped from 10 to 11. This means that downgrading to an earlier version of Realm is not possible and Realm Studio 5.0.0 must be used to view Realm files.

    ✨ Enhancements

    • None.

    🛠 Fixes

    • In some cases a frozen Realm of the wrong version could be returned. (ObjectStore issue #1078)
    • ⬆️ Upgrading files with string primary keys would result in a file where it was not possible to find the objects by primary key. (Core issue #3893, since 7.0.0)
    • NullPointerException when calling toString on RealmObjects with a binary field containing null. (Issue #7084, since 7.0.0)

    Compatibility

    • Realm Object Server: 3.23.1 or later.
    • Realm Studio: 5.0.0 or later.
    • ⬆️ File format: Generates Realms with format v11 (Reads and upgrades all previous formats from Realm Java 2.0 and later).
    • 🚀 APIs are backwards compatible with all previous release of realm-java in the 7.x.y series.

    Internal

    • ⬆️ Upgraded to Object Store commit: 286d7cb2f10c41f89a2efb43b22938610ccad4cf.
    • ⬆️ Upgraded to Realm Sync: 5.0.21.
    • ⬆️ Upgraded to Realm Core: 6.0.24.
  • v7.0.3

    September 01, 2020

    ✨ Enhancements

    • ➕ Added Realm.getNumberOfActiveVersions(), which returns the current number of active versions maintained by the Realm file.

    🛠 Fixes

    • 📌 Creating a query inside a change listener could in some cases result in the version being pinned, which would either drastically increase filesize or cause RealmConfiguration.maxNumberOfActiveVersions() to trigger. (Issue #6977, since 7.0.0)
    • ⬆️ If you upgrade a Realm file where you have "" elements in a list of non-nullable strings, the upgrade would crash.
    • ⬆️ If an attempt to upgrade a Realm file has ended with a crash with "migrate_links" in the call stack, the Realm ended in a corrupt state where further upgrade was not possible. A remedy for this situation is now provided.

    Compatibility

    • Realm Object Server: 3.23.1 or later.
    • Realm Studio: 4.0.0 or later.
    • ⬆️ File format: Generates Realms with format v10 (Reads and upgrades all previous formats from Realm Java 2.0 and later).
    • 🚀 APIs are backwards compatible with all previous release of realm-java in the 7.x.y series.

    Internal

    • ⬆️ Upgraded to Object Store commit: eef80f42e6ede2294eb60f048228012d9b7bc627.
    • ⬆️ Upgraded to Realm Sync: 5.0.19.
    • ⬆️ Upgraded to Realm Core: 6.0.22.
    • ⬆️ The upgrade logic for upgrading fileformats has changed so that progress is now recorded explicitly in a table. This makes the logic simpler and reduces the chance of errors. It will also make it easier to detect if a file has only been partially upgraded.