dsym file

[quote='815439021, faisalIkwal, /thread/815439, /profile/faisalIkwal'] Is there any officially supported way to specify a port range in NENetworkRule? [/quote] I think you’ve answered this yourself (-: If you’d like to see this change in the future, I encourage you to file an enhancement request describing your requirements. And please post your bug number, just for the record. Oh, one more thing. The port range in your example coveres ephemeral ports, which I presume is not a coincidence. If so, consider focusing on that in your ER. The ephemeral port range has changed in the past and it wouldn’t surprise me if it changed again in the future. OTOH, a general port range feature would be more flexible. (One of the nice things about your filing your own ERs is that you get to explain your own requirements in your own words.) [quote='815439021, faisalIkwal, /thread/815439, /profile/faisalIkwal'] Is creating thousands of rules (one per port) considered acceptable or supported? [/quote] Again, I

Apple can fairly say: “Agents shouldn’t directly edit our serialization format.” But if they advertise agentic workflows and the agent can’t reliably do core build/debug tasks (target build settings, linking, schemes), then the product gap is real. Agentic workflows require a closed loop: apply build-setting changes → build → fix → repeat. If the only exposed interface is “chat + inline code edits,” it’s not agentic for build/debugging. Therefore Apple needs a supported automation surface (typed project actions with preview/undo), regardless of how ugly project.pbxproj is. Expected: Agent can apply target/scheme/build-setting changes (typed + preview/undo), run build, iterate on failures. Actual (Xcode 26.3 RC): Agent mostly suggests or edits source files; can’t reliably adjust the build/ debug configuration loop for multi-target/C++ integration. C/C++ integration is where an agent should shine because it’s repetitive, error-driven, and configuration-heavy. A “real” agentic C++ loop in Xcode would ne

@Vincent_Galilieo is right that way it works just make sure your external package doesn't take too much space as the size limit for your zip file is max 25 mb. So @advaitconty just download your packages locally and then create an folder besides your playground and save it there and then while adding packages in Xcode make sure to add that package with the same relative path. ( which is default if you are not editing package.swift file yourself ).

So splitting targets into different projects is a way to go, but do not make cross-project references and add target dependency. The idea is to build the subproject fully separately. Claude helped with implementation, so I asked it to write the rest of the post. The Solution Two scripts, triggered at different build stages: 1. Scheme Pre-Action — BuildPkgTestCMD.sh Builds the CLI project via a separate xcodebuild invocation before the main build starts. 2. Run Script Build Phase — CopyPkgTestCMD.sh Copies the built binary into the app bundle after the Resources phase. Both scripts check EFFECTIVE_PLATFORM_NAME and skip on non-Catalyst builds (e.g. iOS). Gotchas We Hit Build settings leaking into the nested xcodebuild call. Scheme pre-actions inherit all build settings from the parent target as environment variables. This means the nested xcodebuild silently picks up Catalyst platform, signing, and arch settings. Fix: wrap the call with env -i, passing through only selected variables: env -i PATH=$PATH HOME=

thanks; filed https://feedbackassistant.apple.com/feedback/21938996 EPERM upon kill(2) of 'empty' group now

I have run some tests on my copy of StoreKit testing project. When the app is not active, and a renewal comes through, it will be unfinished. The listener task you have in Transaction.updates might not catch it. Question: Does your app handle unfinished transactions? You need to listen for Transaction.unfinished, and finish any verified transactions. Either call it on the next launch, or create another Task to listen for unfinished. func processUnfinishedTransactions() async { for await result in Transaction.unfinished { switch result { case .verified(let verified): // Always finish verified transactions await verified.finish() case .unverified(let unverified, _): // Handle unverified } } } If you check the Understanding StoreKit Workflows sample from WWDC25, notice they have 3 things going on in the Store.swift file: Task(priority: .background) { // Finish any unfinished transactions -- for example, if the app was terminated before finishing a transaction. for await verificationResult in Transaction

Will definitely file bug for clarification. Actually, I verified for another flow where FilterDataProvider is responding with NEFilterNewFlowVerdict.allow() & TransparentProxyProvider is responding with NO. So both FilterDataProvider & TransparentProxyProvider are not interested in this flow, still we see the log line (NetworkExtension) [com.apple.networkextension:] provider rejected new flow TCP headless_shell[{length = 20, bytes = 0xe69023e655b6065e1a2f94fa508807fa43f6ac8a}] remote: 100.72.0.3:443 interface utun9 posted by NetworkExtension framework. Is this logline faulty or not to be taken at its face value ?? This really causes confusion amongst customers when they are trying to debug any network issues.

Hello JoshyMW, This sounds like a serious enough issue to merit a bug report via Feedback Assistant. Can you please open one, and attach your code snippet in the form of a test project, plus any screenshots or documentation you may have? Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Thanks for letting us know, Richard Yeh  Developer Technical Support

So this method falsely returns NSURLRelationshipSame for different directories. One is empty, one is not. Really weird behavior. Do you know where/what the directories were? The problem here is that there's a pretty wide variation between the basic case of a bunch of files and directories sitting on a standard volume and the range of ALL possible edge cases. Two file path URLs pointing to two different file paths have the same NSURLFileResourceIdentifierKey? Yes, this is possible. As one example, the data volume basically ends up in the hierarchy twice meaning that, for example, the path /System/Volumes/Data/Users/ and /Users/ are in fact the same directory. And, yes, getRelationship returns NSURLRelationshipSame for those directories. Now, this: One is empty, one is not. ...is definitely weirder. Ignoring the cache issue below, I don't think you could do it within a standard volume, but you might be able to do it using multiple volumes, particularly duplicated disk image and/or net

Hi @SuyashBel, To run Foundation Models in Simulator, ensure that macOS is up to date. Utilizing Foundation Models framework in the Simulator requires macOS Tahoe, with Apple Intelligence enabled on the Mac. (System Settings -> Apple Intelligence) This will trigger a download of the model, which can also take a little time. Additionally, make sure the simulator is running 26 or later. It can also be helpful to ensure you're using the latest version of Xcode. If everything is updated and you're still having trouble, try restarting your Mac. If all that still fails, let us know and also please file Feedback so we can track this issue. Best, -J

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to this thread. Bug Reporting: How and Why? has tips on creating your bug report.

With the same firmware, OTA testing on the DCL test network was successful in September 2025, and the Home app was able to deliver software update notifications. Since the beginning of 2026, however, the Home app no longer delivers software update notifications. Are you sure about exactly when this started failing? It looks like the TestNet DCL mobile config file (see section 3.2.3. Profile enablement of Apple Matter OTA - User Guide r4) expired on February 7th, at which point this would have stopped working. . I'm working on getting an updated profile released, however, the existing profile should have worked until then unless something else was going wrong. __ Kevin Elliott DTS Engineer, CoreOS/Hardware