You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[CP] Correct warning for compatible Java versions range given template AGP & Gradle versions #136388
Corrects the range of Java versions that flutter create will show if your Java version is incompatible with Flutter's template AGP & Gradle versions and/or is too new/old a version to be recognized by Flutter's tooling.
The range currently printed suggests that the upper bound is inclusive, whereas it is exclusive, so it may confuse developers.
Impacted Users
All Flutter devs running flutter create for something running on Android
Impact Description
They will see a range of Java versions that is confusing. It can easily be found out as incorrect by following documentation linked in the warning, but we can't guarantee devs will look there to confirm the range of Java versions that we suggest.
Workaround
Following the documentation linked in the warning to check the Java versions.
Risk
low
Test Coverage
yes
Validation Steps
There are many tests that prove that the range is exclusive (
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
itsjustkevin commentedon Oct 17, 2023
@reidbaker could you take a look at this cherry-pick and attach the
cp: approvedlabel if you agree?itsjustkevin commentedon Oct 17, 2023
@camsim99 can you link the cherry-pick PR you created?
reidbaker commentedon Oct 17, 2023
Labels added for approval.
camsim99 commentedon Oct 17, 2023
#135710#136766[CP][Android] Update Java/AGP/Gradle warning compatible Java range (#…
[flutter_releases] Flutter stable 3.13.8 Framework Cherrypicks (#136815)
github-actions commentedon Nov 7, 2023
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.