Closed tactical-drone closed 2 years ago
I am currently facing the same problem. I reinstalled visual studio entirely, deleted android studio but after a full fresh setup I currently face the same error again! How did you solve this problem or why is this marked as closed? @tactical-drone
edit: downloading the latest NDK that has a download size worked for me. It seems like the download links are broken.. If newer NDK is needed maybe downloading directly from android could work, but not sure if VS detects this automatically or in which folder they belong. Working with an older NDK seems to work fine in my case.
Hello lovely human, thank you for your comment on this issue. Because this issue has been closed for a period of time, please strongly consider opening a new issue linking to this issue instead to ensure better visibility of your comment. Thank you!
Lovely human. Lol.
I closed it because I made the post in anger. I should learn not to do that.
Description
The latest 17.4 does this when you try to work on maui stuff. (lastnight's RC2 bits)
Pressing accept leads to:
Installing it manually from the Manager yields:
In general, the MAUI workloads are causing all kinds of bugs. There are so many and it's so vast I doubt it needs explanations here. I hope that the release will sort these out.
Steps to Reproduce
Download VS2022 Preview and try to use MAUI.
The out of the box experience will not work, guaranteed.
Link to public reproduction project repository
https://dev.azure.com/unimatrix-zero
Version with bug
7.0 Release Candidate 2
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
microsoft.net.sdk.ios.manifest-7.0.100.msi.x64 (16.0.1475)
Did you find any workaround?
No, even after pulling every conceivable lever.
reinstall vs2022 preview 17.4
reinstall vs2022
delete c:\program files\dotnet
<- good luck fixing such a stupid move. dotnet installers totally brick when you do thisdotnet workload restore
dotnet workload update
dotnet workload install maui
maui-check
Nothing works. There is always some bullshit error that ends in
What boggles the mind is that these are just files. Somehow the files that Microsoft has works, but the ones we have don't work. Or they won't have made the release. How hard can it be to deliver files to a computer. Just boggles the mind.
Relevant log output