Error: Activity class {../MainActivity} does not exist.

[hossam14102010]

Discussed in https://github.com/dotnet/maui/discussions/9510

^{Originally posted by devonuto August 18, 2022} After updating to Microsoft Visual Studio Enterprise 2022 (64-bit) - Preview Version 17.4.0 Preview 1.0 (.NET SDK 6.0.400)

The android emulator isn't in the dropdown as an option to start debugging, only "Windows Machine". When clicking on that, I now get this error:

> am start -a "android.intent.action.MAIN" -c "android.intent.category.LAUNCHER" -n "com.devonuto.myapp/crc6444e428aac7225743.MainActivity"
> Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.devonuto.myapp/crc6444e428aac7225743.MainActivity }
Error type 3
Error: Activity class {com.devonuto.myapp/crc6444e428aac7225743.MainActivity} does not exist.
Failed to launch android application

What has changed? How do I get this working again?

[github-actions[bot]]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

• MAUI will not launch (#16526), similarity score: 0.74

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[dotnet-policy-service[bot]]

Thanks for the issue report @hossam14102010! This issue appears to be a problem with Visual Studio, so we ask that you use the VS feedback tool to report the issue. That way it will get to the routed to the team that owns this experience in VS.

If you encounter a problem with Visual Studio, we want to know about it so that we can diagnose and fix it. By using the Report a Problem tool, you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks.

1. Go to the Visual Studio for Windows feedback tool or Visual Studio for Mac feedback tool to report the issue
2. Close this bug, and consider adding a link to the VS Feedback issue so that others can follow its activity there.

[dotnet-policy-service[bot]]

Thanks for the issue report @hossam14102010! This issue appears to be a problem with Visual Studio (Code), so we ask that you use the VS feedback tool to report the issue. That way it will get to the routed to the team that owns this experience in VS (Code).

If you encounter a problem with Visual Studio or the .NET MAUI VS Code Extension, we want to know about it so that we can diagnose and fix it. By using the Report a Problem tool, you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks.

1. Go to the Visual Studio for Windows feedback tool or .NET MAUI VS Code Extension repository to report the issue
2. Close this bug, and consider adding a link to the VS Feedback issue so that others can follow its activity there.

[drasticactions]

This issue would need to be addressed by the Visual Studio team, since that tooling isn't maintained in this repo. My guess would be that the .NET workloads didn't update along with Visual Studio or are missing on your system. If you go to your command line and type dotnet workload list you should see a MAUI workload. If you don't, that might be why it's missing in your dropdown.

If you install it with dotnet workload install maui and try building your app in the command line (dotnet build), and that works, but still fails within Visual Studio, it could be a VS bug that has to be fixed.