Realm Core v14.13.3

14.13.3 Release notes

Enhancements

• None.

Fixed

• Changing type of primary key column crashes if more than one object (#8056, since v14.13.2)

Breaking changes

• None.

Compatibility

• Fileformat: Generates files with format v24. Reads and automatically upgrade from fileformat v10. If you want to upgrade from an earlier file format version you will have to use RealmCore v13.x.y or earlier.

---

Internals

• None.

---

Realm Core v20.1.1

20.1.1 Release notes

Enhancements

• None.

Fixed

• Migrating primary key to a new type without migration function would cause an assertion to fail. (#8045, since v10.0.0)
• The events library would attempt to upload backup files created as part of file format upgrades, causing backup copies of those backups to be made, looping until the maximum file name size was reached (#8040, since v11.17.0).

Breaking changes

• None.

Compatibility

• Fileformat: Generates files with format v24. Reads and automatically upgrade from fileformat v10. If you want to upgrade from an earlier file format version you will have to use RealmCore v13.x.y or earlier.

---

Internals

• None.

---

Realm Core v14.13.2

14.13.2 Release notes

Enhancements

• None.

Fixed

• Migrating primary key to a new type without migration function would cause an assertion to fail. (#8045, since v10.0.0)
• None.

Breaking changes

• None.

Compatibility

• Fileformat: Generates files with format v24. Reads and automatically upgrade from fileformat v10. If you want to upgrade from an earlier file format version you will have to use RealmCore v13.x.y or earlier.

---

Internals

• None.

---

Realm Core v14.13.1

14.13.1 Release notes

Enhancements

• None.

Fixed

• The events library would attempt to upload backup files created as part of file format upgrades, causing backup copies of those backups to be made, looping until the maximum file name size was reached (#8040, since v11.17.0).

Breaking changes

• None.

Compatibility

• Fileformat: Generates files with format v24. Reads and automatically upgrade from fileformat v10. If you want to upgrade from an earlier file format version you will have to use RealmCore v13.x.y or earlier.

---

Internals

• None.

---

Realm Core v20.1.0

20.1.0 Release notes

Enhancements

• None.

Fixed

• Having a query with a number of predicates ORed together may result in a crash on some platforms (strict weak ordering check failing on iphone) (#8028, since v14.6.0)
• None.

Breaking changes

• None.

Compatibility

• Fileformat: Generates files with format v24. Reads and automatically upgrade from fileformat v10. If you want to upgrade from an earlier file format version you will have to use RealmCore v13.x.y or earlier.

---

Internals

• None.

---

Realm Core v14.13.0

14.13.0 Release notes

Enhancements

• None.

Fixed

• Having a query with a number of predicates ORed together may result in a crash on some platforms (strict weak ordering check failing on iphone) (#8028, since v14.6.0)
• None.

Breaking changes

• Removed http 301/308 redirection support from app services operations provided by App. It is assumed that the SDK's http implementation will handle http redirects instead. (PR #7996)

Compatibility

• Fileformat: Generates files with format v24. Reads and automatically upgrade from fileformat v10. If you want to upgrade from an earlier file format version you will have to use RealmCore v13.x.y or earlier.

---

Internals

• None.

---

Realm Core v14.12.1

14.12.1 Release notes

Enhancements

• None.

Fixed

• Using an empty KeyPath in C API would result in no filtering being done (#7805, since v13.24.0)
• Filtering notifications with backlink columns as last element could sometimes give wrong results (#7530, since v11.1.0)
• Fix crash during client app shutdown when Logger log level is set higher than Info. (#7969, since v13.23.3)
• If File::rw_lock() fails to open a file the exception message does not contain the filename (#7999, since v6.0.21)
• Fallback to hashed filename will fail if length of basename is between 240 and 250 (#8007, since v10.0.0)
• Swift API misuse within a callback from core would result in an internal unreachable error rather than the exception being propagated properly (#7836).

Breaking changes

• None.

Compatibility

• Fileformat: Generates files with format v24. Reads and automatically upgrade from fileformat v10. If you want to upgrade from an earlier file format version you will have to use RealmCore v13.x.y or earlier.

---

Internals

• Update TestAppSession to allow scope-based usage for restarting the local app resources. (PR #7672)

---

Realm Core v14.12.0

14.12.0 Release notes

Enhancements

• Improve sync bootstrap performance by reducing the number of table selections in the replication logs for embedded objects. (#7945)
• Released a read lock which was pinned for the duration of a mutable subscription even after commit. This frees resources earlier, and may improve performance of sync bootstraps where the starting state is large. (#7946)
• Client reset cycle detection now checks if the previous recovery attempt was made by the same core version, and if not attempts recovery again (PR #7944).
• Updated bundled OpenSSL version to 3.3.1. (PR #7947)

Fixed

• Fixed an "invalid column key" exception when using a RQL "BETWEEN" query on an int or timestamp property across links. (#7935, since v14.10.1)
• Fixed conflict resolution bug related to ArrayErase and Clear instructions, which could sometimes cause an "Invalid prior_size" exception to prevent synchronization (#7893, since v14.8.0).
• Fixed bug which would prevent eventual consistency during conflict resolution. Affected clients would experience data divergence and potentially consistency errors as a result. (PR #7955, since v14.8.0)
• Fixed issues loading the native Realm libraries on Linux ARMv7 systems when they linked against our bundled OpenSSL resulting in errors like unexpected reloc type 0x03. (#7947, since v14.1.0)
• Realm::convert() would sometimes incorrectly throw an exception claiming that there were unuploaded local changes when the source Realm is a synchronized Realm (#7966, since v10.7.0).

Breaking changes

• None.

Compatibility

• Fileformat: Generates files with format v24. Reads and automatically upgrade from fileformat v10. If you want to upgrade from an earlier file format version you will have to use RealmCore v13.x.y or earlier.

---

Internals

• Reverted the bfd linker override in the Linux-armv7 toolchain file because the upstream OpenSSL issue it was working around was resolved.

---

Realm Core v14.11.2

14.11.2 Release notes

Enhancements

• Sync log statements now include the app services connection id in their prefix (e.g Connection[1:<connection id>] Session[1]: log message) to make correlating sync activity to server logs easier during troubleshooting ((PR #7849)[https://github.com//pull/7849]).

Fixed

• Sync client may report duplicate compensating write errors (#7708, since v14.8.0).

Breaking changes

• None.

Compatibility

• Fileformat: Generates files with format v24. Reads and automatically upgrade from fileformat v10. If you want to upgrade from an earlier file format version you will have to use RealmCore v13.x.y or earlier.

---

Internals

• Fix emscripten build and add emscripten debug/release compile tasks to evergreen. (PR #7916)
• Subscription set state change notifications now work in a multiprocess-compatible manner (PR #7862).

---

Realm Core v14.11.1

14.11.1 Release notes

Enhancements

• None.

Fixed

• App subscription callback was getting fired before the user profile was retrieved on login, leading to an empty user profile when using the callback. (#7889, since v14.7.0)

Breaking changes

• The websocket error codes websocket_client_too_old, websocket_client_too_new, and websocket_protocol_mismatch along with their C API constants were removed. These corresponded to errors the legacy C++ server could have sent, but the baas sync server never did. Any platform networking implementations that surfaced these errors can report a websocket_fatal_error instead if an unknown error occurs during the websocket handshake. If a client connects that is too old or too new, it will finish the websocket handshake and then receive an in-band sync ERROR message that will be handled by the sync error handler. PR #7917

Compatibility

• Fileformat: Generates files with format v24. Reads and automatically upgrade from fileformat v10. If you want to upgrade from an earlier file format version you will have to use RealmCore v13.x.y or earlier.

---

Internals

• None.

---