How could win32 packaged applications use custom capability APIs

[awrff]

Hi, team

I run ESim APIs to fetch ESim id on Windows devices and it works in UWP applications.
Due to my application framework restrictions, I have to use this api in a Win32 packaged application. Other APIs with device capability or restrict capability could run normally but this custom API failed.
I want to know why this api failed and if this is a bug. Because other APIs also require capability declaration in UWP yet they could work in Win32 applications.

details:
The api failed on ESimManager.TryCreateESimWatcher(), which always reutrned null.
The doc says it should return A new instance of the ESimWatcher class, or null if the caller's user security identifier (SID) is not authorized by the Windows service that handles eSIM-related operation requests.
I'm confused with this SID decription. How does it work in custom capability funtions? Why other APIs don't require this.

[stevewhims]

Thanks, @awrff, I'll investigate this issue with the product team.

-Steve