this post was submitted on 26 Dec 2023
16 points (94.4% liked)

.NET MAUI

119 readers
4 users here now

founded 11 months ago
MODERATORS
SmartmanApps@programming.dev
16
Solved: Latest Visual Studio update causes older Android emulator deployments to fail "Emulator is not ready to be used" (programming.dev)
submitted 10 months ago* (last edited 9 months ago) by SmartmanApps@programming.dev to c/dotnetmaui@programming.dev
16 comments fedilink hide all child comments
 

For details see VS 17.8.3 Android emulator API 28 deployment fails "Emulator is not ready to be used" and please upvote the issue

you are viewing a single comment's thread
view the rest of the comments
[–] Lmaydev@programming.dev 2 points 10 months ago* (last edited 10 months ago) (3 children)

There's a good thread here about that error here: https://github.com/microsoft/winget-cli/issues/3068

Looks like it's either an old version or the cache is corrupted. Theres serveral fixes to try in there.

Can you install anything in Winget?

[–] SmartmanApps@programming.dev 2 points 10 months ago

This is the first time I've ever used Winget. I'll have a read through the thread and try some things out, and let you know how I go. Thanks!

[–] SmartmanApps@programming.dev 1 points 10 months ago (1 children)

Woo hoo! I got it to work. I needed to run it in powershell as admin, and the Id needed to be in quotes, and it worked! I now have 17.8.0 installed, and deployment to my API 28 Android emulator is working - I can actually start developing on my new computer now. :-) Thank you so much for your help!

[–] Lmaydev@programming.dev 2 points 10 months ago

Ah that's amazing mate 😁 Happy coding. Hopefully they get the issue resolved soon.

[–] SmartmanApps@programming.dev 1 points 10 months ago (1 children)

P.S. Would I need to uninstall Visual Studio first?

[–] Lmaydev@programming.dev 2 points 10 months ago (1 children)

Not sure. But I likely would

[–] SmartmanApps@programming.dev 2 points 10 months ago

BTW I tried without uninstalling first to see what would happen, and in essence it went "there's already an installation, checking for upgrades, there are no upgrades available, doing nothing", so looks like you could do it if upgrading, but doesn't work for downgrading - have to start fresh for a downgrade.