Target Android Framework Not Settable Via UI

[david-maw]

Description

The project properties dialog Application section under "Android Targets" has a couple of drop-down boxes to set "Target Android Framework" and "Minimum Target Android Framework" however, the drop downs are both empty.

Steps to Reproduce

1. Create a default MAUI program and build it for android
2. Check Properties/Application/Android Targets the input boxes will be empty and so will the pulldowns.
   

Link to public reproduction project repository

No response

Version with bug

Unknown/Other

Is this a regression from previous behavior?

Yes, this used to work in Xamarin.Forms

Last version that worked well

Unknown/Other

Affected platforms

Android

Affected platform versions

Windows 11

Did you find any workaround?

Yes, either edit the android manifest directly or by using the manifest editor in Properties/Android?

Relevant log output

No response

[ghost]

Thanks for the issue report @david-maw! 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.

[drasticactions]

This is Visual Studio tooling specific for Android, and not controlled under this repo.

[david-maw]

ok, will do. Until then, is there a way to edit the project file to avoid the following warning about mismatched levels?
...AndroidManifest.xml : warning XA4211: AndroidManifest.xml //uses-sdk/@android:targetSdkVersion '33' is less than $(TargetFrameworkVersion) ''. Using API-34 for ACW compilation.
I generally prefer to suppress warnings I understand so as not to get in the habit of ignoring warnings in general. If not, oh well once #19027 is fixed the workaround can go away and I probably won't care anyway.

I've omitted the diatribe about, "you're one company, just transfer the incident report", because I've worked for a large corporation...

[david-maw]

Looks like it's already reported here, I'll add my workaround and a back reference to this report. I'm still interested in a project file workaround if anyone has one.

[jfversluis]

Looks like this has already been reported in the right place and there is nothing much for us to do on our side for right now. Closing this as such, thanks!