Debugging a Package doesn't respect Capabilities

[catmanjan]

Describe the bug

I only found this because I kept submitting my app to the microsoft store and it kept getting rejected

It seems the debug target Package doesn't respect the Capabilities tag

So I was missing the internetAccess capability which was only an issue when installing a deployed version of the package

Steps to reproduce the bug

1. Do an internet request without the internetAccess capability
2. You can still do it when debugging

Expected behavior

No response

Screenshots

No response

NuGet package version

None

Windows version

No response

Additional context

No response

[snigdha011997]

Hi @catmanjan , can you please provide minimal repro app for the further investigation?

[DarranRowe]

To ask, has Windows and Visual Studio themselves been properly ruled out?

Windows itself because this is what installs the package (using developer mode, see here). Windows is also what controls network traffic, such as Windows.Networking.Sockets and Windows.Web.Http.

Visual Studio, because of the debugger.

On Windows 11 24H2, (26100.4652) with Visual Studio 2022 17.14, the following desktop console application fails with access denied as expected.

#include <Windows.h>

#undef GetCurrentTime

#include <winrt/Windows.Foundation.h>
#include <winrt/Windows.Foundation.Collections.h>
#include <winrt/Windows.Web.h>
#include <winrt/Windows.Web.Http.h>

int wmain()
{
	winrt::init_apartment();

	winrt::Windows::Web::Http::HttpClient http_client{};
	winrt::Windows::Foundation::Uri test_uri{ L"https://www.microsoft.com" };

	auto result = http_client.GetAsync(test_uri).get();

	return 0;
}

Have you tried similar code to see if a desktop application without the Windows App SDK referenced shows the same issue?