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

top 16 comments
sorted by: hot top controversial new old
[-] Lmaydev@programming.dev 3 points 10 months ago* (last edited 10 months ago) 
winget install --id=Microsoft.VisualStudio.2022.Community -v "17.8.0" -e

Try this as a workaround

[-] SmartmanApps@programming.dev 1 points 10 months ago

winget install --id=Microsoft.VisualStudio.2022.Community -v "17.8.0" -e

Thanks - everything I could find said you can't do it for Community edition - but that didn't work. Is there a particualr directory I need to be in or something?

[-] Lmaydev@programming.dev 2 points 10 months ago* (last edited 10 months ago)

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

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

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

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

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.

[-] SmartmanApps@programming.dev 1 points 10 months ago

@Ategon@programming.dev The dotnetmaui bot here failed to boost this into Mastodon for some reason.

[-] SmartmanApps@programming.dev 1 points 10 months ago

Just an update on this. There's been an update to the issue on the 10th of January with "Under Investigation. This issue is currently being investigated...", which is a nice change from "more info needed", or even worse "this isn't a bug it's a feature", so they've managed to reproduce the bug and are looking into it.

This means if you see the 17.8.4 update available message, the fix isn't in there, so don't update yet. I'm using 17.8.0 - I'm not sure if the bug was introduced in 17.8.1, 17.8.2, or 17.8.3, but 17.8.0 is definitely safe to use.

[-] SmartmanApps@programming.dev 1 points 9 months ago

17.9 is available now, and I can confirm it is working again now :-)

[-] SmartmanApps@programming.dev 1 points 9 months ago

[-] SmartmanApps@programming.dev 1 points 9 months ago

[-] SmartmanApps@programming.dev 1 points 9 months ago

๐Ÿ˜‚Now that the Mastodon bots are working again I just realised the issue with just posting screenshots in here - the Mastodon post is empty! ๐Ÿ˜‚So for those following via Mastodon, the Android emulator issue is fixed and is currently available via preview (but I'll be waiting for the non-preview release. I'm presuming this is the next one, or maybe the one after that. Whatever the latest preview version is).

[-] SmartmanApps@programming.dev 1 points 9 months ago

Well, 17.8.6 just came out, so I'm guessing this fix will be in 17.8.7 then.

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

.NET MAUI

119 readers
1 users here now

founded 11 months ago
MODERATORS
SmartmanApps@programming.dev