Manual migration to androidx/target sdk 28 #14
Merged
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.
This may be useful now or later - it seems like this androidx stuff will replace android.support - though it seems like you can't mix&match.
I haven't looked that much into this yet - but it seems like it would make sense for plugins to have dual support (a migrated vs unmigrated version) so you don't end up in version hell - one way for this can obviously just be using old versions of plugins if you're not ready to migrate your flutter app to androidx. This seems to be what flutter is favoring.
See:
Flutter migration: https://flutter.dev/docs/development/packages-and-plugins/androidx-compatibility
Android migration: https://developer.android.com/jetpack/androidx/migrate