-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Adding a note about the Android Studio Flamingo gradle mismatch #8501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Dropping my ping to shams here for reference -- It looks like the image urls on this staging link is referencing localhost - so the local staging version might have been pushed to Firebase instead of the built static files! @sfshaza2 try running |
|
@sfshaza2 Was the go link go/android-android-gradle-error intended to be go/android-java-gradle-error? |
src/release/breaking-changes/android-java-gradle-migration-guide.md
Outdated
Show resolved
Hide resolved
src/release/breaking-changes/android-java-gradle-migration-guide.md
Outdated
Show resolved
Hide resolved
src/release/breaking-changes/android-java-gradle-migration-guide.md
Outdated
Show resolved
Hide resolved
| [splitting out ApplicationId from PackageName][]. | ||
| If this occurs, downgrade to the 7.6 release of | ||
| Gradle. | ||
| * If, as part of this fix, you upgraded to Flutter 3.10 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This bullet seems completely orthogonal, no? Upgrading to Flutter 3.10 is not connected to upgrading Android Studio.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I'm just a tad worried that folks might upgrade to 3.10 (thinking it might help), and then be really screwed. Especially because there is a new command in 3.10 which tells you if you have this incompatibility situation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd be more explicit then, I think. Rather than saying "as part of this fix", should we simply say "upgrading to Flutter 3.10 does not fix this problem"?
src/release/breaking-changes/android-java-gradle-migration-guide.md
Outdated
Show resolved
Hide resolved
| updates the Java SDK from 11 to 17, which | ||
| isn't compatible with the version of the Java SDK | ||
| used to build the app's Gradle file when the project | ||
| was originally created with `flutter create`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Long run-on sentence?
Co-authored-by: Parker Lougheed <parlough@gmail.com>
…de.md Co-authored-by: Parker Lougheed <parlough@gmail.com>
ericwindmill
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The instructions worked and are easy to follow.
src/release/breaking-changes/android-java-gradle-migration-guide.md
Outdated
Show resolved
Hide resolved
src/release/breaking-changes/android-java-gradle-migration-guide.md
Outdated
Show resolved
Hide resolved
| shell script's `JAVA_HOME` environment variable. | ||
| * If `JAVA_HOME` isn't defined, Flutter looks | ||
| for any `java` executable in your path. | ||
| Once [issue 122609][] lands, the `flutter doctor` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is only landing for 3.10 right? or will anyone using flutter doctor in previous releases also get this fix so that they can depend on it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it being issue 122609
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
??? I don't know what we advise here.
|
|
||
| ### Not yet released to stable | ||
|
|
||
| * [Android Java Gradle migration guide][] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm this feels weird to be under not yet release to stable, currently there is nothing in the guide that depends on the next stable release for developers to follow it and unblock themselves when using Flamingo.
if we add the flutter analyze --suggestions tool steps into the guide then it has something that is not yet released to stable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. I can just take it out of the index.
src/release/breaking-changes/android-java-gradle-migration-guide.md
Outdated
Show resolved
Hide resolved
| change the `distributionUrl` field to the new Gradle version: | ||
|
|
||
| ```properties | ||
| distributionUrl=https\://services.gradle.org/distributions/gradle-8.0.2-all.zip |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should suggest updating to a version that starts with 7 not the latest gradle.
This is for 2 reasons. In my own updates of our owned examples we have had fewer issues, sometimes non when updating to 7.3.3 (minimum) or 7.6.1 (newest 7.* version released in feb) and run into significantly more issues moving to 8.*.
Second is that the gradle tooling as a policy has one major version of depreciation cycle before removal. So assuming their gradle code did have something deprecated it is more likely to exist in major version 7 and removed in 8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per https://gradle.org/whats-new/gradle-8/#upgrades, it looks like users should upgrade to 7.6.1 as an intermediary state, even if they're ultimately moving to 8.x -- so I agree that we should make that our target throughout this doc.
src/release/breaking-changes/android-java-gradle-migration-guide.md
Outdated
Show resolved
Hide resolved
src/release/breaking-changes/android-java-gradle-migration-guide.md
Outdated
Show resolved
Hide resolved
|
@Updated. Please review again @timsneath @mariamhas @reidbaker |
| updates its bundled Java SDK from 11 to 17. | ||
| Flutter uses the version of Java bundled with | ||
| Android Studio to build Android apps. | ||
| Gradle versions [prior to 7.3][] can't run |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this supposed to have a link?
timsneath
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking great. Thank you so much for all your work to make this transition less painful for customers! I'm sure we'll keep tweaking this page over the coming week, but it's a solid LGTM from me!
This PR supercedes PR #8490.
Staged here:
main page: https://parlough-android-flutter.web.app/
migration page: https://parlough-android-flutter.web.app/release/breaking-changes/android-java-gradle-migration-guide
the "go" link: https://parlough-android-flutter.web.app/go/android-java-gradle-error
(This is the staged go link. The actual go link will be docs.flutter.dev rather than
parlough-android-flutter.web.app.)@reidbaker @camsim99 @mariamhas @ericwindmill @redbrogdon @timsneath