Right now, the debugging of iOS physical devices is performed via TCP/IP under the hood, even if you connect your device via USB.
This has a side effect, which is that it's most likely that the first time you install your app, iOS will show a prompt asking you to allow finding and connecting devices to your local network. See the image below for reference:
This prompt will cause that the first time the user tries to debug an app, it will fail to connect the debugger and hit breakpoints.
This has an easy workaround, which is the user needs to click Allow on the prompt and also it needs to launch the app again for debugging (F5). From the second time on, debugging will work fine.
To avoid this known issue, debugging via USB needs to be implemented, so we avoid TCP/IP and the iOS prompts.
Describe the feature you'd like
Right now, the debugging of iOS physical devices is performed via TCP/IP under the hood, even if you connect your device via USB.
This has a side effect, which is that it's most likely that the first time you install your app, iOS will show a prompt asking you to allow finding and connecting devices to your local network. See the image below for reference:
This prompt will cause that the first time the user tries to debug an app, it will fail to connect the debugger and hit breakpoints. This has an easy workaround, which is the user needs to click
Allowon the prompt and also it needs to launch the app again for debugging (F5). From the second time on, debugging will work fine.To avoid this known issue, debugging via USB needs to be implemented, so we avoid TCP/IP and the iOS prompts.
There's a bug related to this: https://github.com/microsoft/vscode-dotnettools/issues/770
The bug will be closed as a known issue since there's a clear workaround, and we will use this suggestion ticket to implement the feature.
Alternatives considered
Click
Allowon the prompt and launch the app again for debugging (F5). From the second time on, debugging will work fine.Environment Information