Skip to content

Don't update Android SDK settings in build.gradle.#8089

Merged
jakobr-google merged 1 commit intoflutter:masterfrom
jakobr-google:sdk-stamp
Feb 14, 2017
Merged

Don't update Android SDK settings in build.gradle.#8089
jakobr-google merged 1 commit intoflutter:masterfrom
jakobr-google:sdk-stamp

Conversation

@jakobr-google
Copy link
Contributor

Instead of detecting the installed Android SDKs, and always updating the build.gradle file to use the latest (which might be a preview, or otherwise might not work), let's just use what the build.gradle file specifies.

I believe the main rationale behind always updating the SDK versions was to make the build Just Work with what's installed on the user's computer. However, if we just leave the version to what the user has set it to, Gradle will automatically download the specified SDK, if the user has accepted the licenses in SDK Manager. So things will still work, and the build will no longer depend on whatever SDKs you happened to have installed on your machine.

Fixes #5638.

@devoncarew
Copy link
Contributor

I believe the main rationale behind always updating the SDK versions was to make the build Just Work

That was the rational, but it sounds like things will continue working w/o this change, and we won't be doing things like modifying the user's build.gradle as a side effect of running an app. lgtm!

@jakobr-google jakobr-google merged commit cd3fd47 into flutter:master Feb 14, 2017
@jakobr-google jakobr-google deleted the sdk-stamp branch February 14, 2017 13:48
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Newbie question: changing android build tools in flutter "hello-services" example

4 participants