dotnet/aspire

[WebToolsE2E][Aspire] With SDK 8.0.300 + Aspire 8.0 GA, dotnet new aspire-starter does not work due to manifest provider returned a duplicate manifest ID 'microsoft.net.sdk.android'.

v-elenafeng opened this issue · 9 comments

v-elenafeng commented

INSTALL STEPS

  1. Clean machine: Win11 x64 23h2 ENU

  2. Install SDK 8.0.300

    • Apply feed for SDK 8.0.300

  3. Install Aspire 8.0 GA

    • Apply the "darc-pub-dotnet-aspire" feed for Aspire 8.0 GA

  4. Install cred helper (run from Windows PowerShell admin prompt)

    iex "& { $(irm https://aka.ms/install-artifacts-credprovider.ps1) }"

REPRO STEPS

  1. Run dotnet --info -- works fine

    image

  2. Run dotnet workload list

    image

  3. Run dotnet new aspire-starter -o Aspire-StarterApp01

ACTUAL
Template creation failed

image

EXPECTED
Template creation should succeed

v-elenafeng commented

This issue can also be reproduced with a clean install of VS 17.10 GA (with Aspire 8.0 GA)+ Web workload when creating a new template using the CLI, but works fine using VS.

balachir commented

@joperezr are we missing an additional feed? It seems that 'dotnet new aspire-starter' doesn't work using CLI with above steps.

balachir commented

The error seems similar to an issue that was reported earlier as well - internal Bug 2048871.

balachir commented

Elena and I investigated today and it seems like a possible feed permissions issue. But still, we have two machines that Elena and I setup - she can still reproduce the issue on her machine and I cannot reproduce the issue on my machine. We'll continue doing more investigation on Monday.

v-elenafeng commented

I installed a new machine today and can still reproduce this issue, it happens randomly and the failure rate is about 50%.

image

balachir commented

@joperezr @marcpopMSFT with the correct feeds applied, we seem to still run into this issue about 50% of the time, even within the same Command Prompt session as you can see in Elena's screenshot. Can you investigate, please?

marcpopMSFT commented

To summarize the investigation, there appears to be a parallelism issue within the template engine that affects workload related templates. Daniel is still digging into possible fixes but the short-term workaround (besides the customer just trying again) is to have the aspire templates remove the workload constraint. It should not be necessary within templates provided by workloads and appears to be causing duplicate resolution of the same workload. That's our recommendation for 8.0.1 version of the aspire workload.
https://github.com/dotnet/aspire/blob/main/src/Aspire.ProjectTemplates/templates/aspire-apphost/.template.config/template.json#L26-L31

dsplaisted commented

Here are the details that I found in my investigation: dotnet/templating#7946 (comment)

v-elenafeng commented

Close this issue as it was fixed both on Aspire 8.0.1 and 8.1 Preview 1.