|
| 1 | +10.52.2 Release notes (2024-07-19) |
| 2 | +============================================================= |
| 3 | + |
| 4 | +### Enhancements |
| 5 | + |
| 6 | +* Server-side role and permissions changes no longer require a client reset to |
| 7 | + update the local Realm. ([Core #7440](https://github.com/realm/realm-core/pull/7440)) |
| 8 | + |
| 9 | +### Fixed |
| 10 | + |
| 11 | +* Deleting an object with a `List<AnyRealmValue` proeprty which linked to an |
| 12 | + object which had been deleted by another sync client would switch to the |
| 13 | + incorrect cascade mode and perform a cascading delete. This meant that if any |
| 14 | + subsequent properties in the object linked to another top-level object and |
| 15 | + that was the *only* link to that object, the target object would also be |
| 16 | + recursively deleted as if it was an embedded object. |
| 17 | + ([Core #7828](https://github.com/realm/realm-core/issues/7828), since v10.51.0). |
| 18 | +* Fix the assertion failure `array_backlink.cpp:112: Assertion failed: |
| 19 | + int64_t(value >> 1) == key.value` when removing links to an object (either by |
| 20 | + reassigning the link or by deleting the object). This could happen if the link |
| 21 | + came from a collection inside a `AnyRealmValue`, any `Map`, or a |
| 22 | + `List<AnyRealmValue>`, and there were more than 256 objects of the type which |
| 23 | + contained the link. |
| 24 | + ([Core #7594](https://github.com/realm/realm-core/issues/7594), since v10.8.0) |
| 25 | +* Fix the assertion failure `array.cpp:319: Array::move() Assertion failed: |
| 26 | + begin <= end [2, 1]` when deleting objects containing collections nested |
| 27 | + inside a `AnyRealmValue` when this caused bptree leaves to be merged. |
| 28 | + ()[Core #7839](https://github.com/realm/realm-core/issues/7839), since v10.51.0). |
| 29 | +* `SyncSession.wait(for .upload)` was inconsistent in how it handled commits |
| 30 | + which do no produce any changesets to upload (such as modifying flexible sync |
| 31 | + subscriptions). Previously if all unuploaded commits had empty changesets and |
| 32 | + the session had never completed a download it would wait for download |
| 33 | + completion, and otherwise it would complete immediate. It now always |
| 34 | + completes immediately. ([Core #7796](https://github.com/realm/realm-core/pull/7796)). |
| 35 | +* The sync client could hit an assertion failure if a session is resumed while |
| 36 | + the session is being suspended. ([Core #7860](https://github.com/realm/realm-core/issues/7860), since v10.27.0) |
| 37 | +* If a sync session was interrupted by a disconnect or restart while downloading |
| 38 | + a bootstrap (a set of downloads caused by adding or changing a query |
| 39 | + subscription), stale data from the previous bootstrap could be included when |
| 40 | + the session reconnected and completed downloading the bootstrap. This could |
| 41 | + lead to objects stored in the database that do not match the actual state of |
| 42 | + the server and potentially leading to compensating writes. |
| 43 | + ([Core #7827](https://github.com/realm/realm-core/issues/7827), since v10.27.0) |
| 44 | +* Fixed unnecessary server roundtrips when there was no download to acknowledge |
| 45 | + ([Core #2129](https://jira.mongodb.org/browse/RCORE-2129), since v10.51.0). |
| 46 | + |
| 47 | +### Compatibility |
| 48 | + |
| 49 | +* Realm Studio: 15.0.0 or later. |
| 50 | +* APIs are backwards compatible with all previous releases in the 10.x.y series. |
| 51 | +* Carthage release for Swift is built with Xcode 15.4.0. |
| 52 | +* CocoaPods: 1.10 or later. |
| 53 | +* Xcode: 15.1.0-16 beta 3. |
| 54 | + |
| 55 | +### Internal |
| 56 | + |
| 57 | +* Upgraded realm-core from v14.10.2 to 14.11.0 |
| 58 | + |
1 | 59 | 10.52.1 Release notes (2024-06-28) |
2 | 60 | ============================================================= |
3 | 61 |
|
|
0 commit comments