VS Code launches two iPhones simulators on .net maui app Debug.
- Dominant language
- C#
- Stars
- 23.3k
- Forks
- 2k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 297
Description
### Description
I use VS Code for .net maui app development. When I debug iOS version of it, VS Code starts the "Simulator" app and for some reason two iPhone simulators are launched: one with what I want it to launch (iPhone 17 Pro), and another one with iPhone 16e. I can close the unwanted iPhone 16e simulator, but it will still be launched again the next time I debug the app.
### Steps to Reproduce
1. Right-click .net maui project in Solution Explorer pane in VS Code.
2. Choose Debug -> Start New Instance.
3. If you did the previous step for the first time, you will be asked a few questions by displaying various screens in "Command Palette" at the top. When it asks about the simulator, choose "iPhone 17 Pro". I think it will also ask to select the startup project. Choose your .net maui app project. (By the way, why does it ask this if I initiated this by right-clicking this project..)
4. If you did the step 2) earlier, and need to change the configuration so that the "Debug -> Start New Instance" launches iOS simulator rather than, say Mac Catalyst, you need to click "{}" icon at the bottom right of the Status Bar, then in the window that appear, click "Launch Configuration" item. In the screen which appears at the top, choose "iPhone 17 Pro". Then do step 2).
5. When Simulator is finally launched, you will probably see two simulator windows (at least, this is what I get): one window with iPhone 17 Pro which you wanted, and another window with iPhone 16e, which you did not want.
### Link to public reproduction project repository
_No response_
### Version with bug
10.0.30
### Is this a regression from previous behavior?
Not sure, did not test other versions
### Last version that worked well
Unknown/Other
### Affected platforms
iOS
### Affected platform versions
macOS 15.7.3; VS Code 1.108.2; XCode 26.2; Workload version: 10.0.102; maui 10.0.1/10.0.100; SDK 10.0.100
### Did you find any workaround?
No
### Relevant log output
```shell
```
Contributor guide
Assessment
This issue has not been assessed yet.