All Versions
275
Latest Version
Avg Release Cycle
14 days
Latest Release
9 days ago

Changelog History
Page 8

  • v5.5.0 Changes

    October 12, 2020

    ✨ Enhancements

    • ➕ Add the ability to capture a NotificationToken when using a Combine publisher that observes a Realm Object or Collection. The user will call saveToken(on:at:) directly after invoking the publisher to use the feature.

    🛠 Fixed

    • When using Realm.write(withoutNotifying:) there was a chance that the supplied observation blocks would not be skipped when in a write transaction. (Object Store #1103)
    • Comparing two identical unmanaged List<>/RLMArray objects would fail. (#5665).

    Compatibility

    • ⬆️ File format: Generates Realms with format v11 (Reads and upgrades all previous formats)
    • Realm Object Server: 3.21.0 or later.
    • Realm Studio: 5.0.0 or later.
    • 🚀 APIs are backwards compatible with all previous releases in the 5.x.y series.
    • 🚀 Carthage release for Swift is built with Xcode 12.

  • v5.4.8 Changes

    October 05, 2020

    🛠 Fixed

    • Case-insensitive equality queries on indexed string properties failed to clear some internal state when rerunning the query. This could manifest as duplicate results or "key not found" errors. (#6830, #6694, since 5.0.0).

    Compatibility

    • ⬆️ File format: Generates Realms with format v11 (Reads and upgrades all previous formats)
    • Realm Object Server: 3.21.0 or later.
    • Realm Studio: 5.0.0 or later.
    • 🚀 APIs are backwards compatible with all previous releases in the 5.x.y series.
    • 🚀 Carthage release for Swift is built with Xcode 12.

    Internal

    • ⬆️ Upgraded realm-core from v6.1.3 to v6.1.4
    • ⬆️ Upgraded realm-sync from v5.0.28 to v5.0.29

  • v5.4.7 Changes

    September 30, 2020

    🛠 Fixed

    • Equality queries on indexed string properties would sometimes throw "key not
      found" exceptions if the hash of the string happened to have bit 62 set.
      (.NET #2025, since v5.0.0).
    • Queries comparing non-optional int properties to nil would behave as if they
      were comparing against zero instead (since v5.0.0).

    Compatibility

    • ⬆️ File format: Generates Realms with format v11 (Reads and upgrades all previous formats)
    • Realm Object Server: 3.21.0 or later.
    • Realm Studio: 5.0.0 or later.
    • 🚀 APIs are backwards compatible with all previous releases in the 5.x.y series.
    • 🚀 Carthage release for Swift is built with Xcode 12.

    Internal

    • ⬆️ Upgraded realm-core from v6.1.2 to v6.1.3
    • ⬆️ Upgraded realm-sync from v5.0.27 to v5.0.28

  • v5.4.6 Changes

    September 29, 2020

    ⚡️ 5.4.5 failed to actually update the core version for installation methods other than SPM. All changes listed there actually happened in this version for non-SPM installation methods.

    Compatibility

    • ⬆️ File format: Generates Realms with format v11 (Reads and upgrades all previous formats)
    • Realm Object Server: 3.21.0 or later.
    • Realm Studio: 5.0.0 or later.
    • 🚀 APIs are backwards compatible with all previous releases in the 5.x.y series.
    • 🚀 Carthage release for Swift is built with Xcode 12.

    Internal

    • ⬆️ Upgraded realm-sync from v5.0.26 to v5.0.27

  • v5.4.5 Changes

    September 28, 2020

    ✨ Enhancements

    • 🐎 Slightly (<5%) improve the performance of most operations which involve reading from a Realm file.

    🛠 Fixed

    • Rerunning a equality query on an indexed string property would give incorrect results if a previous run of the query matched multiple objects and it now matches one object. This could manifest as either finding a non-matching object or a "key not found" exception being thrown. (#6536, since 5.0.0).

    Compatibility

    • ⬆️ File format: Generates Realms with format v11 (Reads and upgrades all previous formats)
    • Realm Object Server: 3.21.0 or later.
    • Realm Studio: 5.0.0 or later.
    • 🚀 APIs are backwards compatible with all previous releases in the 5.x.y series.
    • 🚀 Carthage release for Swift is built with Xcode 12.

    Internal

    • ⬆️ Upgraded realm-core from v6.1.1 to v6.1.2
    • ⬆️ Upgraded realm-sync from v5.0.25 to v5.0.25

  • v5.4.4 Changes

    September 25, 2020

    ✨ Enhancements

    • 👌 Improve the asymtotic performance of NOT IN queries on indexed properties. It is now O(Number of Rows) rather than O(Number of Rows * Number of values in IN clause.)

    🛠 Fixed

    • Fix a crash inside realm::Array(Type)::init_from_mem() which would sometimes occur when running a query over links immediately after creating objects of the queried type. (#6789 and possibly others, since 5.0.0).
    • Possibly fix problems when changing the type of the primary key of an object from optional to non-optional.

    Compatibility

    • ⬆️ File format: Generates Realms with format v11 (Reads and upgrades all previous formats)
    • Realm Object Server: 3.21.0 or later.
    • Realm Studio: 5.0.0 or later.
    • 🚀 APIs are backwards compatible with all previous releases in the 5.x.y series.
    • 🚀 Carthage release for Swift is built with Xcode 12.

    Internal

    • ⬆️ Upgraded realm-core from v6.0.26 to v6.1.1
    • ⬆️ Upgraded realm-sync from v5.0.23 to v5.0.25

  • v5.4.3 Changes

    September 21, 2020

    🛠 Fixed

    • 🛠 Fix compilation via Carthage when using Xcode 12 (#6717).

    Compatibility

    • ⬆️ File format: Generates Realms with format v11 (Reads and upgrades all previous formats)
    • Realm Object Server: 3.21.0 or later.
    • Realm Studio: 3.12 or later.
    • 🚀 APIs are backwards compatible with all previous releases in the 5.x.y series.
    • 🚀 Carthage release for Swift is built with Xcode 12.

  • v5.4.2 Changes

    September 17, 2020

    ✨ Enhancements

    • ➕ Add prebuilt binary for Xcode 12 to the release package.

    🛠 Fixed

    • 🛠 Fix Archiving the Realm and RealmSwift frameworks with Xcode 12. (#6774)

    Compatibility

    • ⬆️ File format: Generates Realms with format v11 (Reads and upgrades all previous formats)
    • Realm Object Server: 3.21.0 or later.
    • Realm Studio: 3.12 or later.
    • 🚀 APIs are backwards compatible with all previous releases in the 5.x.y series.
    • 🚀 Carthage release for Swift is built with Xcode 12.

  • v5.4.1 Changes

    September 16, 2020

    ✨ Enhancements

    • ➕ Add prebuilt binary for Xcode 11.7 to the release package.

    🛠 Fixed

    • 🛠 Fix deadlocks when opening a Realm file in both the iOS simulator and Realm Studio (#6743, since 5.3.6).
    • 🛠 Fix Springboard deadlocking when an app is unsuspended while it has an open Realm file which is stored in an app group on iOS 10-12 (#6749, since 5.3.6).
    • 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 5.0.0)
    • Confining a Realm to a serial queue would throw an error claiming that the queue was not a serial queue on iOS versions older than 12. (#6735, since 5.0.0).
    • Results would sometimes give stale results inside a write transaction if a write which should have updated the Results was made before the first access of a pre-existing Results object. (#6721, since 5.0.0)

    Compatibility

    • ⬆️ File format: Generates Realms with format v11 (Reads and upgrades all previous formats)
    • Realm Object Server: 3.21.0 or later.
    • Realm Studio: 3.12 or later.
    • 🚀 APIs are backwards compatible with all previous releases in the 5.x.y series.
    • 🚀 Carthage release for Swift is built with Xcode 11.7.

    Internal

    • ⬆️ Upgraded realm-core from v6.0.25 to v6.0.26
    • ⬆️ Upgraded realm-sync from v5.0.22 to v5.0.23

  • v5.4.0 Changes

    September 09, 2020

    This version bumps the Realm file format version. This means that older
    🔖 versions of Realm will be unable to open Realm files written by this version,
    and a new version of Realm Studio will be required. There are no actual format
    🔄 changes and the version bump is just to force a re-migration of incorrectly
    ⬆️ upgraded Realms.

    🛠 Fixed

    • ⬆️ Upgrading pre-5.x files with string primary keys would result in a file where
      realm.object(ofType:forPrimaryKey:) would fail to find the object.
      (#6716, since 5.2.0)
    • A write transaction which modifies an object with more than 16 managed
      properties and causes the Realm file to grow larger than 2 GB could cause an
      assertion failure mentioning "m_has_refs". (JS #3194, since 5.0.0).
    • Objects with more than 32 properties could corrupt the Realm file and result
      in a variety of crashes. (Java #7057, since 5.0.0).

    Compatibility

    • ⬆️ File format: Generates Realms with format v11 (Reads and upgrades all previous formats)
    • Realm Object Server: 3.21.0 or later.
    • Realm Studio: 3.12 or later.
    • 🚀 APIs are backwards compatible with all previous releases in the 5.x.y series.
    • 🚀 Carthage release for Swift is built with Xcode 11.6.

    Internal

    • ⬆️ Upgraded realm-core from v6.0.23 to v6.0.25
    • ⬆️ Upgraded realm-sync from v5.0.20 to v5.0.22