Skip to content

Conversation

@dellis1972
Copy link
Contributor

Fixes #2433

We should be using the latest versions of the android tooling
if possible. If we can we should try to match the major version
with the max API level we support. In this case we are on Android
P, API Level 28. So we should be using the 28.x.x versions of
the tooling.

Since not all of the tools have a 28.x.x version, in those cases
we should just use the very latest.

Fixes dotnet#2433

We should be using the latest versions of the android tooling
if possible. If we can we should try to match the major version
with the max API level we support. In this case we are on Android
P, API Level 28. So we should be using the 28.x.x versions of
the tooling.

Since not all of the tools have a 28.x.x version, in those cases
we should just use the very latest.
@jonpryor jonpryor merged commit c523107 into dotnet:master Mar 22, 2019
jonpryor pushed a commit that referenced this pull request Apr 22, 2019
Fixes: #2433

We should be using the latest versions of the Android tooling if
possible, matching the major version with the max API level we
support.  In this case we are on Android Pie, API-28.
Thus we should be using the 28.x.x versions of the tooling.

Update `$(AndroidSdkBuildToolsVersion)` to 28.0.3.  
Update `$(AndroidSdkPlatformToolsVersion)` to 28.0.0.

Since not all of the tools have a 28.x.x version, in those cases we
should just use the very latest.
@github-actions github-actions bot locked and limited conversation to collaborators Jan 31, 2024
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.

3 participants