Align Android build with Flutter 3.35.7 toolchain#134
Open
onevcat wants to merge 2 commits into
Open
Conversation
|
When will this be merged, deprecation is coming soon? What if this commit is tagged as 3.0 so it doesn't break old flutter versions. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
Detail
@YkSix
While testing the impact of PR #133 in the Android demo project, I noticed that the latest version of Flutter showed several warnings. Our project's current Gradle and Kotlin versions will soon be unsupported, so I took the opportunity to update and modernize the toolchain.
These changes are now aligned the ones used within Flutter 3.35.7. This means users on the latest Flutter version should have no issues. However, merging this PR right away could cause compatibility problems for users still on older versions of Flutter due to toolchain differences.
For this reason, I suggest leaving this PR open for a while—until most users have migrated to the new Flutter version. Alternatively, we can merge it if we encounter issues that can't be fixed without upgrading.
Testing