azure install maui does not work

Sergey 25 Reputation points
2024-12-16T18:21:32.2433333+00:00

I have following task in my yaml

- task: DotNetCoreCLI@2
      displayName: 'Install MAUI workloads'
      inputs:
        command: custom
        custom: workload
        arguments: 'install maui'

It worked for months in azure until today, nothing has been changed in yaml file.

Now it takes ~40mins to fail and it fails on different packages like:

Workload installation failed: Downloading microsoft.maui.resizetizer.sdk version 7.0.101 failed

or

Workload installation failed: Downloading microsoft.android.sdk.windows version 33.0.95 failed

sdk version is 8.0.203
update to 8.0.402 changed nothing.

Please advice how it could be fixed.

.NET MAUI
.NET MAUI
A Microsoft open-source framework for building native device applications spanning mobile, tablet, and desktop.
3,838 questions
{count} votes

Accepted answer
  1. VarunTha 11,080 Reputation points Microsoft Vendor
    2024-12-16T21:25:35.6633333+00:00

    Hi Sergey,
    Thank you for reaching out to us on the Microsoft Q&A forum.

    Azure DevOps is currently not supported in the Q&A forums.

    I recommend initiating a new discussion through the Developer Community

    Moderators are readily available there to assist you and provide guidance.

    Please don't forget to Accept answer and close this thread.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Digvijay Chauhan 1 Reputation point
    2024-12-16T18:55:04.85+00:00

    Some more suggestions for you Sergey:

    1. Enabling more detailed logs can provide additional insights into what is failing. so try to add the --verbosity detailed argument to the arguments section in your YAML to get more information on what the issue might be.
    - task: DotNetCoreCLI@2
      displayName: 'Install MAUI workloads'
      inputs:
        command: custom
        custom: workload
        arguments: 'install maui --verbosity detailed'
    
    1. Also Consult Azure DevOps Status Page since there could be ongoing incidents that might explain the issue on the Azure DevOps service status page - since you mention that nothing has changed as far as your pipeline is concerned.

    See: https://status.dev.azure.com/_event/576396499

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.