Update dependencies #142
Merged
Update dependencies #142
Conversation
This file contains 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For the background sync investigation, I'll need to make some changes to the example app (in particular, restructuring dependency injection in the example to allow a database to be used within and outside of the compose UI). Some of these new dependencies don't work that well together with our old Gradle version and Android plugins.
So, as a first step, this updates our build dependencies. The most notable changes are the Gradle update, the Kotlin upgrade to 2.1 and the Android Gradle plugin update. I've also removed some build script workarounds that don't appear to be necessary anymore and fixed a few deprecation warnings.
I have tested the core android integration tests, the supabase-todolist demo on the JVM and Android, the android todolist demo and the unit tests in our Swift SDK after a local build.