[build] fix MAUI Integration
job
#10036
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a list of things I fixed...
dotnet/arcade tasks require .NET 10
The
MAUI Integration
job looks to be failing, because we arebuilding with a .NET 9 SDK:
Earlier in the log says:
Lets try .NET 10 and see if the problem goes away.
The fact we previously had
dotnetQuality: preview
in the yaml:This means we were using a preview version of .NET 9 while .NET 9 was
in development. Makes sense to move to .NET 10 now.
Missing logs
When investigating the failures here, I noticed the
Copy logs
stepwould say:
I added an additional path:
Android SDK licenses fail
xaprepare
was failing to accept Android SDK licenses, due to:We had code checking
$(JavaSdkDirectory)
which looked to be blank,then we fall back to:
Earlier in the build, we have a step that sets:
I updated
OS.cs
to look at$JI_JAVA_HOME
first, which appears touse the right path now.
dotnet.exe
not foundNext we got the error:
script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is
correct and try again.
The path above is missing
s\android\bin\Release\dotnet\dotnet.exe
,where I noticed we were missing this in one yaml template: