Add additional troubleshooting link for loopback and UWA

Clarified that when developer changes the capability, they should uninstall and re install the app to ensure the rules are correctly added.
Also, added an additional link to "How to enable loopback and troubleshoot network isolation (Windows Runtime apps)." https://docs.microsoft.com/en-us/previous-versions/windows/apps/hh780593(v=win.10)#debug-network-isolation-issues
This commit is contained in:
poornagmsft 2021-03-31 15:26:13 -07:00 committed by GitHub
parent 433e5d568d
commit 4cd808141d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -72,6 +72,10 @@ For more information about loopback scenarios, see [Communicating with
localhost
(loopback)](/windows/iot-core/develop-your-app/loopback).
Note: If you are in the middle of developing a UWA application and want to test its loopback, ensure to uninstall and re-install the UWA app if the network capabilties change for whatever reason.
Also, see [How to enable loopback and troubleshoot network isolation (Windows Runtime apps)](https://docs.microsoft.com/en-us/previous-versions/windows/apps/hh780593(v=win.10)#debug-network-isolation-issues).
## Debugging Live Drops
If the issue happened recently, but you find you are not able to reproduce the issue, go to Debugging Past Drops for the appropriate trace commands.
@ -1327,4 +1331,4 @@ The filter stated above with action permit:
</item>
```
The capabilities field in a netEvent was added to the traces in the Windows 10
May 2019 Update.
May 2019 Update.