SwiftUI List performance

Hi Travis, the app that I work on sells eSIMs to our customers. We have the entitlement which allows us to perform a direct installation via the addPlan method of CoreTelephony. We try to educate and guide our customers through the installation wizard that iOS offers, though we have noticed that the steps in the wizard are different from iOS 18 to iOS 26, e.g. some of our customers report that they are not prompted at all with steps such as labeling the eSIM or choosing what to use for mobile data, etc. What would be the best contact, or is there a source on which we could rely on these changes?

SwiftUI view hierarchy is internal to the framework. When using SwiftUI, you won't need to traverse the view hierarchy – If you do, I'd say that you probably aren't on the right track... Having said that, I'm quite curious why you need to traverse the view hierarchy in SwiftUI. Would you mind to share? Best, —— Ziqiao Chen  Worldwide Developer Relations.

“while using multitasking” means reducing the app’s size and displaying it side by side with the Settings screen at the same time. For better understanding, I will attach an image. Ahh, now I understand. So, the first thing to understand here is that a number of our settings (particularly around authorization) don't really have a unauthorize path. That is, many APIs provide a way for an app to check if they're authorized, but they don't have a notification/delegate for you used to be authorized but now you're not. Often this issue is as much architectural as it is API. For example, in the case of Bluetooth you'd need to invalidate all existing Bluetooth objects (since the app doesn't have access anymore) and you'd also need a way to recreate them again (when authorization is restored). All of this is quite unwieldy, so instead of building that architecture, the system just terminates the app instead. As you noticed, this is Allow Tracking“ example: Additionally, I found that YouTube also terminates when the “

Hello @Julsalim , You don't need to programmatically hide the TabBar, it can be done by restructuring your Views. Make sure the NavigationStack contains the TabView, and the Tab contains the NavigationLink. Here's an example view structure that achieves what you're looking for: Also, welcome to iOS Development! SwiftUI is my favorite!  Travis Trotto - DTS Engineer NavigationStack { TabView{ Tab(, systemImage: ) { List{ NavigationLink(... }

Thanks for this very interesting post. I'm not an expert in this field and I invite experts to comment, in my modest opinion, It looks like there’s something unexpected with ObjC/Swift metadata. Can we ask them for a focused sample project that reproduces the issue, can you make a copy of the project that is causing the issue, and then remove everything that isn’t important to keep the meta data in the project that may be causing this? Maybe the linker error you're encountering in Xcode 26.2 after migrating from Xcode 16.2, along with the modifications you've made to the linker flags, points to a deeper issue with how object files are being processed, specifically related to Objective-C runtime data. Could that mean or indicates there is an incompatibility or corruption in Objective-C metadata? Any object files or libraries you're linking were compiled with an older compiler version? Any external libraries or frameworks, with the Xcode 26.2 compiler. If you're using CocoaPods or Carthage, update them ( or ) a

Solved. An iOS 2.0 feaure that I assume is being set automatically by SwiftUI. [[ UIApplication sharedApplication ] setIdleTimerDisabled:true ];

Thanks for the reply. I tried to replace if let result = unarchiver.decodeObject(of: [/* list */], forKey: someKey) as? someClass { by do { let result = try unarchiver.decodeTopLevelObject(of: [/* list */], forKey: someKey) as! someClass It compiles but does not decode: I get a failure on log : unarchiving failed And with this pattern, I do not know how to test the double call within the print Is it an error to use unarchiver.decodeObject ? What can be the side effects ? unarchiver.decodeObject(of: [/* list */], forKey: someKey)

Alright, I have tried to follow your advice and I don't see how this can help. I have this setup: struct AnimatedView: View { @ObservedObject var viewModel: ViewModel var body: some View { let width = viewModel.isExpanded ? 120.0 : 50.0 let height = viewModel.isExpanded ? 400.0 : 100.0 let cornerRadius = viewModel.isExpanded ? 42.0 : 8.0 Color(uiColor: .red) .frame(width: width, height: height) .cornerRadius(cornerRadius) } } The hosting controller is mounted to the top of its parent via constraints. Then I do this in my tap handler for a totally separate button: @objc func tap() { withAnimation(Animation.easeInOut(duration: 0.5), { viewModel.isExpanded.toggle() }) } And what I observe here is that my hosting controller's view immediately teleports to the new frame - its center is immediately in the position where it should be only at the end of the animation. Meanwhile, the SwiftUI content is animating correctly, except it has already teleported. I have tried to use your answer @DTS Engineer I have