-
Notifications
You must be signed in to change notification settings - Fork 537
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bump to xamarin/monodroid@4fa11431 (#6963)
Context: #6965 Changes: http://github.com/xamarin/monodroid/compare/e451ea986b27cdfb965df07c1f2ea74fa14f33c2...f4240bc3c3d331db47c9ee944b4388e0e9af4076 * xamarin/monodroid@4fa114311: Bump to xamarin/android-sdk-installer@223325db (#1248) * xamarin/monodroid@f4240bc3c: Bump to xamarin/android-sdk-installer@68939f22 (#1247) * xamarin/monodroid@f84615dae: Bump to xamarin/android-sdk-installer@69fa0dca (#1245) * xamarin/monodroid@8589f37fa: [ci] Import variables.yaml from xamarin-android (#1246) Update documentation, documenting the new property `$(AndroidManifestType)` and the old targets `GetAndroidDependencies` and `InstallAndroidDependencies`. Fix a "format string parameter count mismatch" between `Properties.Resources.XA5300_Android_Platforms` and the call site within the `<ResolveAndroidTooling/>` task. This avoids a `FormatException` when no API levels can be found. Update the `AndroidDependenciesTests.InstallAndroidDependenciesTest()` to set `$(AndroidManifestType)`=GoogleV2. This opts us into using the "Full" Android SDK packages list, which in turn allows us to install API-32 packages. (The "Supported" list currently doesn't list packages for API-32, meaning the `InstallAndroidDependencies` target won't install API-32, which caused `InstallAndroidDependenciesTest()` to try to fail with XA5300.)
- Loading branch information
Showing
19 changed files
with
97 additions
and
58 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,2 @@ | ||
xamarin/monodroid:main@e451ea986b27cdfb965df07c1f2ea74fa14f33c2 | ||
xamarin/monodroid:main@4fa114311a0ab882c1de1ed265450747a7c34c25 | ||
mono/mono:2020-02@adf1bc4335d710088c58e824b6027255096cc295 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.