Update: I managed to fix it by manually calling: /Applications/Xcode-26.0.0-Beta.4.app/Contents/Developer/usr/bin/actool --version --output-format xml1 In a step before the actual xcodebuild step. It's almost like it caches some kind of state that allows future calls into it to succeed.

I'm here to report that I'm running into exactly the same. Interesting enough: it only happens to some of my xcodebuild commands, even though they're exactly the same apart from the package they're testing. So, I have a self-hosted GitHub Actions pipeline. The first package tested runs into this error: /Applications/Xcode-26.0.0-Beta.4.app/Contents/Developer/usr/bin/xcodebuild -scheme SimulatorCapturing -destination platform=macOS -resultBundlePath /Users/avanderlee/Developer/actions-runner/_work/RocketSim/RocketSim/fastlane/../build/reports/SimulatorCapturing.xcresult -parallel-testing-enabled NO CI=true RECORD_SNAPSHOTS= build test But the next steps don't. This is an example of a another step that succeeds: [13:27:40]: ▸ /Applications/Xcode-26.0.0-Beta.4.app/Contents/Developer/usr/bin/xcodebuild -scheme ShellKit -destination platform=macOS -resultBundlePath /Users/avanderlee/Developer/actions-runner/_work/RocketSim/RocketSim/fastlane/../build/reports/ShellKit.xcresult -parallel-testing-enabled NO CI=true RECORD_SNAPSHOTS= build test For me as well: this didn't happen with an older Xcode beta. I've also reported this in the Feedback Assistant: FB19231144

While I was writing a lesson for my concurrency course, I ran into the same question. While I looked at the mentioned article, it did not list all upcoming features that come with Approachable Concurrency. Note that this list might change in the future, but as of today, the following features are enabled: Disable Outward Actor Isolation Inference (SE-401) Usability of global-actor-isolated types (SE-434) Global-actor isolated conformances (SE-470) Inferring Sendable for methods and key path literals (SE-418) nonisolated(nonsending) by Default (SE-461) I went ahead and copied all upcoming feature flags for you. Here's the code to use inside your Swift Package: .target( name: "YourPackageTarget", swiftSettings: [ .enableUpcomingFeature("DisableOutwardActorInference"), .enableUpcomingFeature("GlobalActorIsolatedTypesUsability"), .enableUpcomingFeature("InferIsolatedConformances"), .enableUpcomingFeature("InferSendableFromCaptures"), .enableUpcomingFeature("NonisolatedNonsendingByDefault") ] ) Don't forget to update your package tools version: // swift-tools-version: 6.2 Although you can already start using some of these upcoming features since Swift 5.9 / 6.0. ––– Antoine van der Lee — Founder of SwiftLee Teaching Concurrency at swiftconcurrencycourse.com

Thanks a lot for these insights, but I lack the answer I was looking for. What exact message/notification is send from an AVCaptureDevice towards AVCaptureSession that will result in finished the startRunning method? Once I know this, I can simulate a connected hardware device and help thousands of developers work on their camera apps in the Simulator.

[quote='834618022, DTS Engineer, /thread/780287?answerId=834618022#834618022'] If you disabled network logging in your library and shipped it to a bunch of folks, that’d seriously compromise your ability to debug problems that only show up in the field. [/quote] I believe we're on the same page, yet, I want it to be opt-in. I'm offering a debug mode for my library, but I at least want to offer a way to enable/disable it. Right now, I'm cluttering the console for implementors without a way for them to always turn it off. If all 3rd party libraries would enable logging without a way to turn it off, developers would have to configure all kinds of category filters inside Xcode. That doesn't sound like something we should want?

To me, it feels like the Network framework should provide an option to enable debug logging or not. In fact, it turns out I could do that for some of those logs: let privacyContext = NWParameters.PrivacyContext(description: "Logging Disabled") privacyContext.disableLogging() // Disable system logging for this context However, there are still quite some logs emitted. [quote='834382022, DTS Engineer, /thread/780287?answerId=834382022#834382022'] Why isn’t that sufficient in your case? [/quote] Xcode filtering is something you'll have to configure again and again, I am never interested in these logs so I want them to be hidden always. On top of that, I'm providing a library to 3rd party developers which I'm now annoying with logs from the Network framework that I'm not even interested in myself. Let me know if that makes sense!

For those visiting here and looking for an up to date answer, I just published this article: https://www.avanderlee.com/debugging/network-link-conditioner-utility/ Apple's Network Link Conditioner works great for macOS testing, but if you're testing your iOS apps, I highly recommend checking out this tool: https://youtu.be/xK3iI5TzuA4 It only affects the app you're testing on the iOS Simulator and keeps your Mac's connectivity untouched: you can still enjoy a blazing fast network condition while your Simulator's app becomes slow. This is a crucial difference as you can keep your development flow going, use tools like AI to find answers, and properly support slow networking in your apps.

Only parasocially, in that I read your blog. Ah, that's so cool! Make me proud to see Apple developers read my content too 💪 Please do. Honestly, I don’t think there’s enough there to do what you want, but it’s good to confirm that before you go off to file your ERs. Dang, you're completely right. This helps a ton already for what I want to built! Thanks a lot! Nope. CoreHID is a new high-level API to interact with HID devices, and iOS devices aren’t those. Perfect, that clarifies a lot and saves me some time investigating that library.

Oh, hey Antoine! Sounds like we know each other? 🙈 AFAIK there’s no API to do this sort of thing. There is the devicectl tool. Have you played around with it already? I have checked it out, but didn't find evidence of it being my answer. I'll have to check out the new stuff, though! However, I did wonder whether this new framework has anything to do with communicating to connected iPhones: https://developer.apple.com/documentation/CoreHID

Thanks a lot, this helps a ton! I'll check out the NETransparentProxyProvider and loop back in case it doesn't work out.

I'm building RocketSim (https://www.rocketsim.app), a developer tool that already works for the Simulator. RocketSim shows a side window next to the Simulator, and would potentially also show it next to an iPhone Mirror. The idea is to add actions like that allow developers to write automations like: Login using a username/password (requiring an API to submit text) Tap a button, fill in text, tap another button aka app navigation automation (requires both text input and UI interaction) Developers have to perform many repetitive interactions in their apps during debugging, so it would be awesome if I could automate that for real devices! Additionally, an API to enable developer settings like: Network conditioner Accessiblity settings

After some further investigation, it turns out that the HEVC video gets transcoded into MPEG-4, even though we've configured our PHPickerViewController as follows: var configuration = PHPickerConfiguration() configuration.selectionLimit = 0 configuration.preferredAssetRepresentationMode = .current return PHPickerViewController(configuration: configuration) We're loading the file using itemProvider.loadFileRepresentation(forTypeIdentifier: "public.movie"), which I believe should be correct. A few interesting findings: If I Airdrop the file to my Mac, it remains being HEVC and keeps the correct size If I load that file into the Xcode Simulator and add it to our app running in the Simulator, transcoding is not taking place The latter is especially interesting: What is the difference between the file on the device vs. the file in the Simulator after airdropping? Why does transcoding take place on device and not in the Simulator? I'd almost say there's some kind of device setting or iCloud influencing the result, but at this point, I've got no clue. Looking forward to get your thoughts!

Thanks for those insights! It seems that there's still a scenario. We've been able to reproduce the user's behavior as follows: Create a video in GoPro Quik Export it to the Photos app Import it into the WeTransfer app <- This is where we use PHPickerViewController in combination with .current Notice a difference in file size as reported by the Photos app Even though the video is locally stored (not in iCloud), a "Preparing..." progress popup appears. That indicates transcoding is happening. I've attached a few screenshots to indicate our issue. Could it be that there's still some kind of setting we're missing to indicate our app allows any kind of file to be added?

When I deactivate an extension I still see it in systemextensionsctl list but it’s flagged as deactivated I see the same; the extension is deactivated. However, my app is still installed in /Application with the deactivated extension. Re-running from Xcode 14.2 and macOS 13.2.1 (22D68) I couldn't get my new build to execute. I did find another way to solve it without restarting: Remove application from /Applications Press continue to confirm it will delete the app's extension Clean my Trash bin Re-run the app This is a quick enough timeline, but obviously, ideally, I would just re-run from Xcode and have my latest Network Extension code working.

Is your start method called? What about your stop method? If so, what’s do you see passed to the reason parameter? I managed to find the cause, I was using true for both: let providerConfiguration = NEFilterProviderConfiguration() providerConfiguration.filterSockets = true providerConfiguration.filterPackets = true After changing filterPackets to false my extension didn't stop anymore! I’m not sure I undertand this question. However, the code snippet you posted in reasonable enough. Perfect, that's all I need to know right now! After my extension started working, I was able to disallow all incoming requests and verified my concept. Btw, I found a small improvement in your guideline: https://developer.apple.com/forums/thread/725805 The next issue you’ll find is that choosing Product > Run runs the app from the build products directory rather than the Applications directory. To fix that: Edit your app’s scheme again. On the left, select Debug. Debug was a bit unclear to me at first. I would better understand this if it was named Run. Btw, your instructions helped big time!