Repository navigation
Conversation
This branch has not been deployed
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
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.
Problem
The Android host for the Navigator 2 example pins Gradle 8.10.2, Android Gradle Plugin 8.7.0, and Kotlin Gradle Plugin 1.8.22. All three are below the build-time minimums enforced by Flutter 3.50.0, so the example needs a toolchain update to produce an APK on that SDK.
Changes
compilerOptionsDSL and retain the Java and Kotlin JVM 11 output targets.The four changes are confined to
example_nav2/android. The related #3488 targetslatest-getx5-RC. This PR brings the Android host update tomaster.Validation
flutter build apk --debug --no-pub --target-platform android-arm64completed with dependency validation enabled. The default Flutter artifact server returned HTTP 403 locally, so verification used the documented Flutter artifact mirror and a local Google Maven fallback.unawaited_return_in_try_blockwarning. The two example counter fixtures also fail on the base commit because their expected counter text is absent from the current screens.