This repository was archived by the owner on Oct 6, 2022. It is now read-only.
Update dependency io.realm:realm-gradle-plugin to v5.15.2#74
Open
renovate[bot] wants to merge 1 commit intodevelopfrom
Open
Update dependency io.realm:realm-gradle-plugin to v5.15.2#74renovate[bot] wants to merge 1 commit intodevelopfrom
renovate[bot] wants to merge 1 commit intodevelopfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.9.1->5.15.2Release Notes
realm/realm-java
v5.15.2Enhancements
Fixed
nullvalues were not printed correctly when usingRealmResults.asJSON()(Realm Core Issue #3399)Date's did not serialize correctly. Only relevant if using Query-based Synchronization. (Realm Core issue #3388)java.lang.IllegalStateException: The following changes cannot be made in additive-only schema modewhen opening an old Realm created between Realm Java 5.10.0 and Realm Java 5.13.0. (Issue #6619, since 5.13.0).Compatibility
Internal
8416010.v5.15.1Enhancements
Fixed
flatDirsrepositories defined crashed the build withMissingPropertyException. (Issue #6610, since 5.15.0).Compatibility
Internal
v5.15.0Enhancements
SyncConfiguration.Builder.clientResyncMode(). (Issue #6487)Fixed
Permission deniedwhen opening a Realm file after an app upgrade or factory reset. This does not automatically fix already existing Realm files. See this FAQ entry for more details. (Issue #5715)Realm.copyToRealm()andRealm.insertOrUpdate()crashed on model classes if@LinkingObjectswas used to target a field with a re-defined internal name in the parent class (e.g. by using@RealmField). (Issue #6581)Compatibility
Internal
9f19d79.v5.14.0Deprecated
SyncCredentials.nickname()has been deprecated in favour ofSyncCredentials.usernamePassword().SyncCredentials.IdentityProvider.NICKNAMEhas been deprecated in favour ofSyncCredentials.IdentityProvider.USERNAME_PASSWORD.Enhancements
Fixed
Compatibility
Internal
v5.13.1Enhancements
Fixed
Compatibility
Internal
bcc6a75v5.13.0Enhancements
Fixed
Compatibility
Internal
f0d7526v5.12.0Enhancements
SyncManager.refreshConnections()that can be used to manually trigger a reconnect for all sessions. This is useful if the device has been offline for a long time or fail to detect that it regained connectivity. (Issue #259)RealmResults.asJson()in@Betathat returns the result of the query as a JSON payload (#6540).Fixed
PermissionManagerstopped working if an intermittent network error was reported. (Issue #6492, since 3.7.0)app_name, which in some cases conflicted with theapp_namedefined by applications. (Issue #6536, since 4.3.0)Compatibility
Internal
7c3ff82v5.11.0NOTE: This version is only compatible with Realm Object Server 3.21.0 or later.
Enhancements
RealmQuery.includeLinkingObjects(). This is only relevant for Query-based Realms and tells subscriptions to include objects linked through@LinkingObjectsfields as part of the subscription as well. Objects referenced through objects and lists are always included as a default. (Issue #6426)RealmQuery.in()queries. (Realm Core PR #3250).Fixed
downloadableBytesvalue sent byProgressListeners.canCreatebut notcanUpdateprivileges on a class, the user would be able to create the object, but not actually set any meaningful values on that object, despite the rule that objects created within the same transaction can always be modified.RealmResultwould cause the object to no longer be part of the query result. (Issue #6478, since 5.8.0).Compatibility
Internal
e4b1314v5.10.0Enhancements
createdAt,updatedAt,expiresAtandtimeToLive. These make it possible to better reason about and control current subscriptions. (Issue #6453)RealmQuery.findAllAsync(String name, boolean update),RealmQuery.subscribe(String name, boolean update)orSubscription.setQuery(RealmQuery query). (Issue #6453)Fixed
Long.MAX_VALUEorLong.MIN_VALUEbut instead clamp to their respective value. (Issue #2722)Compatibility
Internal
e9819edConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.