dsym file

First off, I want to start with a clarification here: We are in a logical deadlock. The kernel dispatches a probe command before UserCreateTargetForID returns, and both of our methods for handling this command result in a permanent hang of the registration process: Calling UserCreateTargetForID means please create the storage stack for this target. Returning from it means I've finished creating the storage stack for this target. I'm not sure how far up the stack you'll actually get, but it's conceivable that we'd get all the way through partition map interpretation and (possibly) volume format detection BEFORE UserCreateTargetForID returns. You're basically guaranteed to get I/O request before UserCreateTargetForID returns. [1] I think the upper levels of the SAM stack prevent this by returning from state before calling registerForService on their IOStorage family nubs, but there's no technical reason why they'd HAVE to work this way. That leads to here: We mark the target as Ready during the UserInitializeTa

@itsme_joris Thanks I see the bug number. Thanks for filing this. @denisa_toderean1 Why don't you think is related to Universal Links? Is your app registering universal links with a link to a AASA file? Thanks Albert Pascual
  Worldwide Developer Relations.

hi @sopmac , I just downloaded and tested the sample and can see the cube's color updating for me & another person. My steps: Sign and run the sample (please make sure your developer team has the group activities capability) press start shareplay -> choose a nearby person aligned views tapped on the cube & we both saw it update Could you please either file a feedback report with all of the details or provide your steps and any updates you made to the sample here? Thank you! note: one other thing is that if both people that are signing it don't have the same team, SharePlay may not work. This isn't an issue in a production app, but if both people download the sample and sign it with different teams, there's a chance that you get an alert that you don't have the same bundle ID so you can't start a SharePlay session.

Hey @Stefko, There's no supported way to perform feet tracking with the APIs currently available. If you'd like us to consider adding the necessary functionality, please file an enhancement request using Feedback Assistant. Please include as much information as your use case as you can to help us understand your needs. Once you file the request, please post the FB number here. If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why? Thanks, Michael

Also confirmed this is still broken in iOS 26.3 (23D127). My feedback is FB21078443 filed Nov 2025. If anyone can’t repro it, here’s a minimal example. Tap a color, then swipe back from the left edge—the source view will disappear after the transition. Easier to repro on physical device, but also possible in sim with a solid swipe. import SwiftUI struct ContentView: View { @Namespace private var namespace private let colors: [Color] = [.red, .blue] var body: some View { NavigationStack { VStack(spacing: 16) { ForEach(colors.indices, id: .self) { index in NavigationLink(value: index) { RoundedRectangle(cornerRadius: 16) .fill(colors[index]) .frame(maxWidth: .infinity, minHeight: 200, maxHeight: 200) .matchedTransitionSource(id: index, in: namespace) } .buttonStyle(.plain) } } .padding(20) .navigationTitle(Zoom Transition Issue) .navigationSubtitle(Tap card, then swipe back from left edge) .navigationDestination(for: Int.self) { index in Rectangle() .fill(colors[index]) .ignoresSafeArea() .navigationTr

Reproducing the issue is easy. Just copy the code from the initial description in a project and launch it on any iOS 26.2+ device after deleting Safari from it. It is not possible to delete Safari from any simulator. I think this issue has nothing to do with my app universal links. I don't know what disabling the link and checking swctutils file means...

Hello Albert, This is reproducible in the iOS 26.2 & iOS 26.3 official releases, not beta versions. So this seems to be an iOS 26.x bug that I can't seem to be mentioned anywhere. The links I'm talking about are both regular, simple links (think https://www.apple.com/apple-events/), the kind that would instantly open in the default browser, as well as universal links, none of them open. No external links seem to open using UIApplication.shared.open(url, options:) when Safari has been removed. If its eases communication, I already filed a feedback ticket FB21867922. I'll link to the app in the ticket there.

Hi Travis, Thanks for the reply. I actually found the issue. Problem was arising due to the assets file being in Development Assets in Build Settings. So Image was not displaying in devices where I installed the app from TestFlight.

[quote='815354021, JacobHearst, /thread/815354, /profile/JacobHearst'] OSLogStore … it only collects logs for the current process [/quote] Correct, at least on everything except the Mac. I cover this and many other logging topics in Your Friend the System Log. There isn’t truly a happy path here. When it comes to NE debugging, you need to see the full system log and there are no APIs on iOS that’ll let you get that. Oh, one last thing. If you’re goal is to work with Apple to help debug a problem, you can ask your user to file a bug in Feedback Assistant. That’ll attach a sysdiagnose log to the bug report. You won’t be able to see the sysdiagnose log, but if you pass the Apple folks that bug number they should be able to get it. I talk more about this idea in Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[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 ).