-
Notifications
You must be signed in to change notification settings - Fork 870
Bump realm-gradle-plugin from 10.9.0 to 10.11.0 #6130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump realm-gradle-plugin from 10.9.0 to 10.11.0 #6130
Conversation
|
historically upgrades from realm 10.9.0+ have introduced runtime crashes, this may however have been a side effect of the android plugin version, it's worth rebasing and double checking after #6141 is merged |
Bumps [realm-gradle-plugin](https://github.com/realm/realm-java) from 10.9.0 to 10.11.0. - [Release notes](https://github.com/realm/realm-java/releases) - [Changelog](https://github.com/realm/realm-java/blob/v10.11.0/CHANGELOG.md) - [Commits](realm/realm-java@v10.9.0...v10.11.0) --- updated-dependencies: - dependency-name: io.realm:realm-gradle-plugin dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
0cdb95f to
2d654da
Compare
mnaturel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After rebase on develop, I have done some tests. No crash but the decryption of messages is very slow or sometimes seems not done at all (not happening with current version of develop). Maybe related to Realm performances?
|
Kudos, SonarCloud Quality Gate passed! |
|
rebased on the current develop the app feels a little faster? I haven't noticed any issues either, have done multiple sign in/sign out and clearing cache doing the same tests with 10.10.1 encounters the native database crashes almost instantly upgrading form 10.10.1 to 10.11.0 crashes with with no apparent way to fix the broken database |
ouchadam
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should merge this after the next release in case we need to revert
|
@dependabot rebase |
|
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
|
After rebase on develop, I have done some new tests on my side as well: update a version using 10.9.0 to the one using 10.11.0, install a version from scratch using 10.11.0. I didn't have any crash or unexpected behavior. |








Bumps realm-gradle-plugin from 10.9.0 to 10.11.0.
Changelog
Sourced from realm-gradle-plugin's changelog.
... (truncated)
Commits
1f02a9dMerge branch 'releases' of https://github.com/realm/realm-java into releases33977c1Release 10.11.02d35852Release 10.11.0aaa1bd5Merge branch 'master' into releasesde8b2dbUpdated changelog for latest contributions (#7677)79d1ed0Upgrade to latest Core (#7676)04ff1c9fix for distinct function (#7639)330964dFixed some typos (#7646)1e53e21Changed deprecated method offer to trySend (#7648)b2e3d90Fix copyToRealmOrUpdate for managed objects in multi module projects (#7661)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)