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
Context: xamarin/android-sdk-installer@2b4d1a6
Changes: xamarin/monodroid@5784a74...b12a3e8
* xamarin/monodroid@b12a3e8d5: Bump to xamarin/android-sdk-installer@2b4d1a6 & xamarin/xamarin-android/master@d583b7c (#1107)
* xamarin/monodroid@3d84feddd: Bump to xamarin/xamarin-android/master@f0d565fe (#1106)
* xamarin/monodroid@ec2931825: Bump to xamarin/android-sdk-installer@c6c12db0 (#1105)
Sometimes, `<InstallAndroidDependencies/>` would fail when running on
Windows, a'la:
…\Xamarin\Android\Xamarin.Installer.Common.targets(12,3): Cannot access a disposed object.
Object name: 'SslStream'.
A fix for the `ObjectDisposedException` has been brought in via the
`android-sdk-installer` bump in xamarin/monodroid@b12a3e8d.
The `<InstallAndroidDependencies/>` test previously had issues due to
clean up logic in the test framework that partially deleted the newly
provisioned Android SDK on a subsequent build. I believe that we've
been seeing successful results for this test because the subsequent
build in the test would fall back to a different Android SDK that was
already on disk. The test has been improved by asserting that the
newly installed Android SDK is used during the subsequent build.
0 commit comments