SwiftUI List performance

Hello @mlbonniec , thank you for your question! I believe what you are looking for is raycast(from:to:query:mask:relativeTo:). You can perform a raycast on the Scene that an Entity belongs to. If you configure an entity with ManipulationComponent, you can subscribe to the event ManipulationEvents.WillRelease to execute code when a person releases an object. Then, you can perform a raycast on the scene downward from the entity's position and place the entity on the closest surface. Here's a quick implementation I threw together demonstrating how to position an Entity on raycast hit: // This code runs when a person releases an object. func handleManipulationWillRelease(event: ManipulationEvents.WillRelease) { // Start the raycast from the position of the entity when it is released. let raycastStart = event.entity.position // End the raycast one meter below the starting point (surfaces further away than 1m will be ignored). let raycastEnd = raycastStart + [0, -1, 0] // Perform the rayc

I investigated further and found your answer! UndoManager is the API in the Foundation framework for undo/redo and SwiftUI has an environment value for that undoManager. This example disables undo on TextField on Mac struct ContentView: View { @Environment(.undoManager) var undoManager: UndoManager? var body: some View { VStack { TextField(Test, text: $text) } .task { undoManager?.disableUndoRegistration() } } } Let me know if this answers your question  Travis Trotto - DTS Engineer

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

just have a go and look through these forums... 75% of topics over here are regarding this issue, some people are on months long waiting list without any reply for support tickets. Me personally, I'm only a week deep in this 48hrs max enrollment target / 2 bussines days max to reply to a support ticket, but reading these forums I already braced myself for at least another month or so... it's a joke of a 4 trilion dollar company.

Sorry for not replying earlier. No, I'm afraid that info isn't what I'm looking for. The thing that I'd like to understand really is, specifically: how to use the built-in undo support of SwiftUI TextField views, if any. Hopefully you're able to get details on this somehow!

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

I contacted them and they never replied. This issues appears to be with how Asset Packs are queried by App Store Connect. I just went to approve new versions of Asset Packs for external testing, and all Asset Packs for all my apps are displayed in the list

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=

Hi Kevin, Thank you for your feedback and the feedback from the engineering team. We have integrated all suggestions from your forum posts (ID: 875288022, 875587022) and the Bug Report, and have conducted a full round of testing. Below is our current status. We now perform a memset on SCSIUserParallelResponse in the ISR and correctly populate the version, fControllerTaskIdentifier, and fBytesTransferred fields. The ISR now differentiates between Bundled/Legacy modes, calling BundledParallelTaskCompletion (without release()) and ParallelTaskCompletion (with release()) accordingly. The aforementioned fixes have resolved all 0x92000006 Panics and DEXT Corpse crashes. Unplugging the hardware or deactivating the DEXT while the driver is in a hung state no longer triggers a panic. 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: Scenario A (Repor