Error reporting when an MSIX app tries to use an API requiring a declared capability at runtime

Fiza_Azmi 

When repackaging existing Win32/.Net Framework apps, IT Pros don't really know what API interfaces will be used.  One area of concern for us is when the application uses an API that requires a capability declaration.

 

It would be very helpful if we could detect that the reason the app fails is that a call was made that required a capability that wasn't declared.  I have been unable to detect any events in the event logs for this issue.

 

Is there a way to detect when this occurs, or if not, can it be added?  This would also be helpful for developers of newer apps (more likely to use APIs requiring the capability) that didn't realize they needed the declaration too.