You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+35-5Lines changed: 35 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,8 @@
1
-
## 10.5.0 (YYYY-MM-DD)
1
+
## 10.6.0-BETA.1 (YYYY-MM-DD)
2
2
3
3
### Breaking Changes
4
+
*[RealmApp] Sync protocol version increased to 3. This version adds support for the new data types introduced in file format version 21.
5
+
* File format version bumped to 21. In this version we support new basic datatypes `UUID` and `RealmAny`, as well as `RealmSet` and `RealmMap` collections with string-based keys (i.e. `RealmDictionary`).
4
6
* Queries no longer do nullability checks on non-nullable fields, so using `null` as an argument will not throw an `IllegalArgumentException`.
5
7
* String query filters `contains`, `beginsWith`, `endsWith`, and `like`, now throw a null pointer exception on null values.
6
8
* The query builder no longer throw `IllegalStateException` but `IllegalArgumentException`.
@@ -34,12 +36,40 @@
34
36
* Classes names "class_class_..." were not handled correctly when doing queries ([#4480](https://github.com/realm/realm-core/issues/4480))
35
37
* Fix collection notification reporting for modifications. This could be observed by receiving the wrong indices of modifications on sorted or distinct results, or notification blocks sometimes not being called when only modifications have occurred. ([#4573](https://github.com/realm/realm-core/pull/4573) since v6).
36
38
37
-
### Breaking changes
38
-
* Sync protocol version increased to 3. This version adds support for the new data types introduced in file format version 21.
39
-
* File format version bumped to 21. In this version we support new basic datatypes `UUID` and `RealmAny`, as well as `RealmSet` and `RealmMap` collections with string-based keys (i.e. `RealmDictionary`).
39
+
### Compatibility
40
+
* File format: Generates Realms with format v21. Unsynced Realms will be upgraded from Realm Java 2.0 and later. Synced Realms can only be read and upgraded if created with Realm Java v10.0.0-BETA.1.
41
+
* APIs are backwards compatible with all previous release of realm-java in the 10.6.y series.
42
+
* Realm Studio 10.0.0 or above is required to open Realms created by this version.
40
43
41
44
### Internal
42
-
* Updated to Realm Core commit: <TBD>.
45
+
* Updated to Realm Core 11.0.0-beta.4, commit: d50aef63a8aaf435e3afed82b589b47d8e1ab1ab.
46
+
47
+
48
+
## 10.5.0 (2021-05-07)
49
+
50
+
### Breaking Changes
51
+
*[RealmApp]`SyncSession.State.WaitingForAccessToken` has been added. It represents the local access token not longer being valid, but is automatically being refreshed.
52
+
53
+
### Enhancements
54
+
* We now make a backup of a Realm file prior to any file format upgrade. The backup is retained for 3 months. Backups from before a file format upgrade allows for better analysis of any upgrade failure. We also restore a backup, if a) an attempt is made to open a realm file whith a "future" file format and b) a backup file exist that fits the current file format. The backup file is placed next to the real Realm file and is named `<fileName>.v<realmFileFormatVersion>.backup.realm`.
55
+
* The error message when the intial steps of opening a Realm file fails is now more descriptive.
56
+
57
+
### Fixes
58
+
*[RealmApp] Client Reset errors now correctly forward the server error message. (Issue [#7363](https://github.com/realm/realm-java/issues/7363), since 10.0.0)
59
+
*[RealmApp] All `AppException`s now correctly report the error message through `RuntimeException.getMessage()` instead of only through `AppException.getErrorMessage()`.
60
+
*[RealmApp] Proactively check the expiry time on the access token and refresh it before attempting to initiate a sync session. This prevents some error logs from appearing on the client such as: "ERROR: Connection[1]: Websocket: Expected HTTP response 101 Switching Protocols, but received: HTTP/1.1 401 Unauthorized" (RCORE-473, since v10.0.0).
61
+
* Fix name aliasing not working in sort/distinct clauses of raw string predicates.
62
+
* Fix collection notification reporting for modifications. This could be observed by receiving the wrong indices of modifications on sorted or distinct results, or notification sometimes not being called when only modifications have occured. (since v7.0.0).
63
+
* Make conversion of Decimal128 to/from string work for numbers with more than 19 significant digits. (#4548)
64
+
65
+
### Compatibility
66
+
* File format: Generates Realms with format v20. Unsynced Realms will be upgraded from Realm Java 2.0 and later. Synced Realms can only be read and upgraded if created with Realm Java v10.0.0-BETA.1.
67
+
* APIs are backwards compatible with all previous release of realm-java in the 10.x.y series.
68
+
* Realm Studio 10.0.0 or above is required to open Realms created by this version.
69
+
70
+
### Internal
71
+
* Updated to Realm Core 10.7.1, commit 5043c25e1d8f5971002e0fec85dea5ea3d7eb3d7.
0 commit comments