I grabbed Apple's sample project, SimpleFirewall, here https://developer.apple.com/documentation/networkextension/filtering_network_traffic. The app builds and runs, but when I press the start button it tells me this in the console:2019-06-05 15:00:38.032893-0500 SimpleFirewall[32086:151724] System extension request failed: App containing System Extension to be activated must be in /Applications folderOk, fair enough. Weirdly, the INSTALL_PATH in build settings is pointed to /Applications, but okay, I'll grab the product and the extension and shove it in /Applications myself and worry about how to debug this later. When I try that, it has me open System Preferences to enable the system extension--progress! However, even after that, the Start button on the application, which is intended to start filtering incoming connections, briefly spins and goes back to the red/disabled state.Any tips on how to run this within Xcode and debug it are appreciated. I know it's early and the session doesn't even air until Friday, but there's only so many days left in the summer 🙂.Best,Mark

I just noticed that in Xcode 12 XCTOSSignpostMetric.applicationLaunch is deprecated. But I'm not seeing anywhere in the documentation that alludes to an alternative—so did Apple decide testing app launch in this manner isn't worth it? I know MetricKit and Instruments include app launch data, so it's not like there's no way to measure this. I'm mostly curious about their reasoning since calculating the average of warm launches from the XCTestMetric sounded like the right thing to do in order to get consistent results.