-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[net9.0] Update dependencies from dotnet/android #24539
[net9.0] Update dependencies from dotnet/android #24539
Conversation
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
@jonathanpeppers seems we are getting a error on building the templates.
|
@rmarinho they want to require JDK 17 going forward: There is a workaround if you need to use JDK 11, but I would notify Jon Pryor if you really need to do that. |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
/azp run MAUI-UITests-public |
/azp run MAUI-DeviceTests-public |
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
Azure Pipelines successfully started running 1 pipeline(s). |
|
…0-rc.2.24429.1+azdo.10133834 Microsoft.Android.Sdk.Windows From Version 35.0.0-rc.2.87 -> To Version 35.0.0-rc.2.89
…-e237401724371b999f3113778f50591de5f63ccb-1 Microsoft.Android.Sdk.Windows From Version 35.0.0-rc.2.89 -> To Version 35.0.0-rc.2.93
…-550f66e519b2efddddd864bf9dc8e47e953b031c-1 Microsoft.Android.Sdk.Windows From Version 35.0.0-rc.2.93 -> To Version 35.0.0-rc.2.96
…-ac8a922d495dff28fdc29310d509a21fa139b883-1 Microsoft.Android.Sdk.Windows From Version 35.0.0-rc.2.96 -> To Version 35.0.0-rc.2.99
new one
|
@rmarinho I'm going to revert this for now: To see if that unblocks the build here. |
…<PrepareDSOWrapperState/>` Context: dotnet/maui#24539 (comment) In .NET MAUI's build, they failed to bump .NET for Android because of the following error: dotnet\packs\Microsoft.Android.Sdk.Windows\35.0.0-rc.2.130\tools\Xamarin.Android.Common.Debugging.targets(139,2): error XABLD7009: System.InvalidOperationException: Internal error: archive DSO stub location not known for architecture 'X86' at Xamarin.Android.Tasks.DSOWrapperGenerator.WrapIt(AndroidTargetArch targetArch, String payloadFilePath, String outputFileName, IBuildEngine4 buildEngine, TaskLoggingHelper log) in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Utilities/DSOWrapperGenerator.cs:line 86 at Xamarin.Android.Tasks.BuildApk.AddRuntimeConfigBlob(ZipArchiveEx apk) in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Tasks/BuildApk.cs:line 404 at Xamarin.Android.Tasks.BuildApk.ExecuteWithAbi(String[] supportedAbis, String apkInputPath, String apkOutputPath, Boolean debug, Boolean compress, IDictionary`2 compressedAssembliesInfo, String assemblyStoreApkName) in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Tasks/BuildApk.cs:line 215 at Xamarin.Android.Tasks.BuildApk.RunTask() in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Tasks/BuildApk.cs:line 357 at Microsoft.Android.Build.Tasks.AndroidTask.Execute() in /Users/runner/work/1/s/xamarin-android/external/xamarin-android-tools/src/Microsoft.Android.Build.BaseTasks/AndroidTask.cs:line 25 In 5ebcb1d, we introduced some MSBuild `RegisterTaskObject()` usage that failed in specific way: * MAUI has a `.sln` with multiple "app" projects: device tests, samples, etc. building in parallel * The `<PrepareDSOWrapperState/>` MSBuild task runs for project A, saving x64 and arm64 values. * Project B goes to run `<BuildApk/>` but x86 is missing. For now, we can fix this by using `ProjectSpecificTaskObjectKey()` that wraps the key with a `Tuple` such as: (key, WorkingDirectory) Which, should result in a unique key per project. In a future PR, we could consider removing this `RegisterTaskObject()` usage completely, and doing all the work inside the `<BuildApk/>` MSBuild task instead.
…-7d730228379df63d318603d45a354fe9a2b4274d-1 Microsoft.Android.Sdk.Windows From Version 35.0.0-rc.2.130 -> To Version 35.0.1-ci.main.1
Looking up build with BAR id 240097 Updating 'Microsoft.Android.Sdk.Windows': '35.0.1-ci.main.1' => '35.0.0-rc.2.134' (from build '9.0.1xx-rc2-b795a653460417af9da75f94e4a487a2665faa7f-1' of 'https://github.com/dotnet/android') Checking for coherency updates... Local dependencies updated based on build with BAR id 240097 (9.0.1xx-rc2-b795a653460417af9da75f94e4a487a2665faa7f-1 from https://github.com/dotnet/android@release/9.0.1xx-rc2)
Android |
@jonathanpeppers I think we still see some failures
|
These are debug messages, not an error. The error I'm seeing is:
And then it found no valid JDK 17. I don't think there is a change that caused this, except for us requiring JDK 17 now. |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
@jonathanpeppers does this seem something ? or just random?
|
…<PrepareDSOWrapperState/>` (#9340) Context: dotnet/maui#24539 (comment) In .NET MAUI's build, they failed to bump .NET for Android because of the following error: dotnet\packs\Microsoft.Android.Sdk.Windows\35.0.0-rc.2.130\tools\Xamarin.Android.Common.Debugging.targets(139,2): error XABLD7009: System.InvalidOperationException: Internal error: archive DSO stub location not known for architecture 'X86' at Xamarin.Android.Tasks.DSOWrapperGenerator.WrapIt(AndroidTargetArch targetArch, String payloadFilePath, String outputFileName, IBuildEngine4 buildEngine, TaskLoggingHelper log) in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Utilities/DSOWrapperGenerator.cs:line 86 at Xamarin.Android.Tasks.BuildApk.AddRuntimeConfigBlob(ZipArchiveEx apk) in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Tasks/BuildApk.cs:line 404 at Xamarin.Android.Tasks.BuildApk.ExecuteWithAbi(String[] supportedAbis, String apkInputPath, String apkOutputPath, Boolean debug, Boolean compress, IDictionary`2 compressedAssembliesInfo, String assemblyStoreApkName) in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Tasks/BuildApk.cs:line 215 at Xamarin.Android.Tasks.BuildApk.RunTask() in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Tasks/BuildApk.cs:line 357 at Microsoft.Android.Build.Tasks.AndroidTask.Execute() in /Users/runner/work/1/s/xamarin-android/external/xamarin-android-tools/src/Microsoft.Android.Build.BaseTasks/AndroidTask.cs:line 25 In 5ebcb1d, we introduced some MSBuild `RegisterTaskObject()` usage that failed in specific way: * MAUI has a `.sln` with multiple "app" projects: device tests, samples, etc. building in parallel * The `<PrepareDSOWrapperState/>` MSBuild task runs for project A, saving x64 and arm64 values. * Project B goes to run `<BuildApk/>` but x86 is missing. For now, we can fix this by using `ProjectSpecificTaskObjectKey()` that wraps the key with a `Tuple` such as: (key, WorkingDirectory) Which, should result in a unique key per project. In a future PR, we could consider removing this `RegisterTaskObject()` usage completely, and doing all the work inside the `<BuildApk/>` MSBuild task instead.
…<PrepareDSOWrapperState/>` (#9340) Context: dotnet/maui#24539 (comment) In .NET MAUI's build, they failed to bump .NET for Android because of the following error: dotnet\packs\Microsoft.Android.Sdk.Windows\35.0.0-rc.2.130\tools\Xamarin.Android.Common.Debugging.targets(139,2): error XABLD7009: System.InvalidOperationException: Internal error: archive DSO stub location not known for architecture 'X86' at Xamarin.Android.Tasks.DSOWrapperGenerator.WrapIt(AndroidTargetArch targetArch, String payloadFilePath, String outputFileName, IBuildEngine4 buildEngine, TaskLoggingHelper log) in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Utilities/DSOWrapperGenerator.cs:line 86 at Xamarin.Android.Tasks.BuildApk.AddRuntimeConfigBlob(ZipArchiveEx apk) in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Tasks/BuildApk.cs:line 404 at Xamarin.Android.Tasks.BuildApk.ExecuteWithAbi(String[] supportedAbis, String apkInputPath, String apkOutputPath, Boolean debug, Boolean compress, IDictionary`2 compressedAssembliesInfo, String assemblyStoreApkName) in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Tasks/BuildApk.cs:line 215 at Xamarin.Android.Tasks.BuildApk.RunTask() in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Tasks/BuildApk.cs:line 357 at Microsoft.Android.Build.Tasks.AndroidTask.Execute() in /Users/runner/work/1/s/xamarin-android/external/xamarin-android-tools/src/Microsoft.Android.Build.BaseTasks/AndroidTask.cs:line 25 In 5ebcb1d, we introduced some MSBuild `RegisterTaskObject()` usage that failed in specific way: * MAUI has a `.sln` with multiple "app" projects: device tests, samples, etc. building in parallel * The `<PrepareDSOWrapperState/>` MSBuild task runs for project A, saving x64 and arm64 values. * Project B goes to run `<BuildApk/>` but x86 is missing. For now, we can fix this by using `ProjectSpecificTaskObjectKey()` that wraps the key with a `Tuple` such as: (key, WorkingDirectory) Which, should result in a unique key per project. In a future PR, we could consider removing this `RegisterTaskObject()` usage completely, and doing all the work inside the `<BuildApk/>` MSBuild task instead.
…<PrepareDSOWrapperState/>` (#9340) Context: dotnet/maui#24539 (comment) In .NET MAUI's build, they failed to bump .NET for Android because of the following error: dotnet\packs\Microsoft.Android.Sdk.Windows\35.0.0-rc.2.130\tools\Xamarin.Android.Common.Debugging.targets(139,2): error XABLD7009: System.InvalidOperationException: Internal error: archive DSO stub location not known for architecture 'X86' at Xamarin.Android.Tasks.DSOWrapperGenerator.WrapIt(AndroidTargetArch targetArch, String payloadFilePath, String outputFileName, IBuildEngine4 buildEngine, TaskLoggingHelper log) in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Utilities/DSOWrapperGenerator.cs:line 86 at Xamarin.Android.Tasks.BuildApk.AddRuntimeConfigBlob(ZipArchiveEx apk) in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Tasks/BuildApk.cs:line 404 at Xamarin.Android.Tasks.BuildApk.ExecuteWithAbi(String[] supportedAbis, String apkInputPath, String apkOutputPath, Boolean debug, Boolean compress, IDictionary`2 compressedAssembliesInfo, String assemblyStoreApkName) in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Tasks/BuildApk.cs:line 215 at Xamarin.Android.Tasks.BuildApk.RunTask() in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Tasks/BuildApk.cs:line 357 at Microsoft.Android.Build.Tasks.AndroidTask.Execute() in /Users/runner/work/1/s/xamarin-android/external/xamarin-android-tools/src/Microsoft.Android.Build.BaseTasks/AndroidTask.cs:line 25 In 5ebcb1d, we introduced some MSBuild `RegisterTaskObject()` usage that failed in specific way: * MAUI has a `.sln` with multiple "app" projects: device tests, samples, etc. building in parallel * The `<PrepareDSOWrapperState/>` MSBuild task runs for project A, saving x64 and arm64 values. * Project B goes to run `<BuildApk/>` but x86 is missing. For now, we can fix this by using `ProjectSpecificTaskObjectKey()` that wraps the key with a `Tuple` such as: (key, WorkingDirectory) Which, should result in a unique key per project. In a future PR, we could consider removing this `RegisterTaskObject()` usage completely, and doing all the work inside the `<BuildApk/>` MSBuild task instead.
…<PrepareDSOWrapperState/>` (#9340) Context: dotnet/maui#24539 (comment) In .NET MAUI's build, they failed to bump .NET for Android because of the following error: dotnet\packs\Microsoft.Android.Sdk.Windows\35.0.0-rc.2.130\tools\Xamarin.Android.Common.Debugging.targets(139,2): error XABLD7009: System.InvalidOperationException: Internal error: archive DSO stub location not known for architecture 'X86' at Xamarin.Android.Tasks.DSOWrapperGenerator.WrapIt(AndroidTargetArch targetArch, String payloadFilePath, String outputFileName, IBuildEngine4 buildEngine, TaskLoggingHelper log) in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Utilities/DSOWrapperGenerator.cs:line 86 at Xamarin.Android.Tasks.BuildApk.AddRuntimeConfigBlob(ZipArchiveEx apk) in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Tasks/BuildApk.cs:line 404 at Xamarin.Android.Tasks.BuildApk.ExecuteWithAbi(String[] supportedAbis, String apkInputPath, String apkOutputPath, Boolean debug, Boolean compress, IDictionary`2 compressedAssembliesInfo, String assemblyStoreApkName) in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Tasks/BuildApk.cs:line 215 at Xamarin.Android.Tasks.BuildApk.RunTask() in /Users/runner/work/1/s/xamarin-android/src/Xamarin.Android.Build.Tasks/Tasks/BuildApk.cs:line 357 at Microsoft.Android.Build.Tasks.AndroidTask.Execute() in /Users/runner/work/1/s/xamarin-android/external/xamarin-android-tools/src/Microsoft.Android.Build.BaseTasks/AndroidTask.cs:line 25 In 5ebcb1d, we introduced some MSBuild `RegisterTaskObject()` usage that failed in specific way: * MAUI has a `.sln` with multiple "app" projects: device tests, samples, etc. building in parallel * The `<PrepareDSOWrapperState/>` MSBuild task runs for project A, saving x64 and arm64 values. * Project B goes to run `<BuildApk/>` but x86 is missing. For now, we can fix this by using `ProjectSpecificTaskObjectKey()` that wraps the key with a `Tuple` such as: (key, WorkingDirectory) Which, should result in a unique key per project. In a future PR, we could consider removing this `RegisterTaskObject()` usage completely, and doing all the work inside the `<BuildApk/>` MSBuild task instead.
This pull request updates the following dependencies
From https://github.com/dotnet/android