Incorrect TFM used for F5

[davidortinau]

Type: Bug

I select the target framework net9.0-ios, then I choose the iOS simulator I want, but when I then hit F5 it builds and deploys to Mac Catalyst.

I confirmed the settings from the {} popover.

The chosen device there was my physical phone and not the simulator, so I corrected that. The rest of the settings were as I expected. F5 again and same result, Mac Catalyst.

When I look at the Run and Debug menu I see a debug profile, however I have never created one and I do not see a .vscode folder where this profile can be reviewed or edited.

I see that now there's conflicting info in the status bar area.

If I click around to a xaml file or csproj file and come back to the C# file I lose the {} option.

When I then select the thing that says net9.0-maccatalyst in the left of the status bar I get a totally different style of tfm + device selection, and there's no version information so I have to guess from among 3 different iPhone 16 Pro simulators.

Extension version: 1.10.16
VS Code version: Code - Insiders 1.101.0-insider (7197360b79e6da3404ed5ad1fb4d7ea74a8bb5d2, 2025-06-04T05:03:51.910Z)
OS version: Darwin arm64 24.5.0
Modes:

System Info

Item	Value
CPUs	Apple M4 Max (16 x 2400)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: enabled_on video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	4, 6, 8
Memory (System)	64.00GB (0.64GB free)
Process Argv	--crash-reporter-id 9f9ad6ad-88e1-448d-baf4-d250e72b38cb
Screen Reader	no
VM	0%

A/B Experiments

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt551cf:31249598
vscod805:30301674
vscaat:30438846
c4g48928:30535728
2i9eh265:30646982
962ge761:30841072
dsvsc014:30777825
dsvsc015:30821418
h48ei257:31000450
pythontbext0:30879054
cppperfnew:30980852
dwnewjupyter:31046869
pythonrstrctxt:31093868
nativeloc1:31118317
e80f6927:31120813
dwcopilot:31158714
c3hdf307:31184662
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
hdaa2157:31222309
copilot_t_ci:31222730
g012b348:31231168
pythoneinst12:31251391
bgtreat:31252123
c7cif404:31309980
pythonpulldiag:31287486
6gi0g917:31259950
61ibe868:31282443
996jf627:31264550
pythonrdcb7:31268811
usemplatestapi:31297334
jdghv92:31317040
747dc170:31275146
pythonfullctx:31296836
6518g693:31302842
pylancecolor:31288664
generatesymbolt:31280541
convertfstringf:31280702
gendocf:31280703
923gi514:31310909
j97ad248:31306657
1cfa2231:31320947
a2ijf515:31307742
convertlamdat:31319677
gce3e431:31315077

| VS Bug 2598356

[davidortinau]

btw - My workflow is to exclusively use keyboard. I do CMD+SHFT+P, select a device, and hit F5. Only when things go wrong do I choose to directly pick a TFM or debugger, or to go to the mouse and click on anything in the status bar or debug panel.