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
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.
Copy file name to clipboardExpand all lines: Documentation/workflow/HowToAddNewApiLevel.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,3 +93,16 @@ Enumification work can be delayed and only the final API has to be enumified.
93
93
Note that there are documented and undocumented XML nodes, and we don't have to deal with undocumented ones.
94
94
95
95
Android P introduced no documented XML artifact.
96
+
97
+
7) Update Android Tooling Versions
98
+
99
+
These sre located in [Xamarin.Android.Common.props.in](../../src/Xamarin.Android.Build.Tasks/Xamarin.Android.Common.props.in). The following MSBuild properties need to be updated to ensure
100
+
the latest tool versions are being used.
101
+
102
+
`AndroidSdkBuildToolsVersion`
103
+
`AndroidSdkPlatformToolsVersion`
104
+
`AndroidSdkToolsVersion`
105
+
106
+
The major version should match the new API level. For Android P this will be 28.x.x . If a version which exactly matches the API Level is not available then the latest version should be used.
0 commit comments