SwiftUI List performance

Hi Quinn, Thank you for above pointers. Following it, I found that: The release entitlements file we were using (Ro_ _ IOSS_ _ _n.entitlements) did not include com.apple.developer.payment-pass-provisioning, so the app never claimed it. That’s why App Store Connect flagged the entitlement as missing. **Fixes I made: ** a. Added this key (entitlement) to RoboIOSSiren.entitlements manually: com.apple.developer.payment-pass-provisioning and updated aps-environment to production aps-environment production b. After (a) I did below in order: Clean + Archive In Xcode: Product > Clean Build Folder… Then: Product > Archive Verify entitlements in the archive In Organizer, select the new archive → Distribute App → Custom → App Store Connect → Export On the “Review IPA content” screen, confirm the entitlements list now includes: com.apple.developer.payment-pass-provisioning Upload using Transporter Upload the exported .ipa with Transporter. Check App Store Connect Wait for processing and re-check the TestF

Hello @thisisjaymehta, Welcome to SwiftUI development! 🥳 The first thing I would look at is the Attributes menu, located in the Inspector area (the sidebar on the right of Xcode). You can also quickly open this tab by pressing ⌥ ⌘ 4. In that menu you will notice options for devices, appearances, sizes and more. In your screenshot, it appears you have the Scales set to Single Scale. You can try switching this to Individual Scale and add different scales which are configured to show on different devices. You can find more information about how to do that here Fitting images into available space If not, try appearances and see if it's a light/dark mode issue. It looks like you already did some troubleshooting by setting a solid white color background. A great tip you can use to check both color schemes easily is by using this toggle at the bottom of the canvas in Xcode, which will show both the light and dark move preview in Canvas. For more information on Xcodes canvas see Previewing your app’s interf

Hello @isaacweisberg, I see the UIKit example on the right is animating correctly to me. It looks like you followed the steps correctly: Line 75 of ViewController.swift the UIHostingController observes .preferredContentSize. Nice work on implementing that! 😎👍 Can you clarify on what you mean? Are you trying to achieve the same effect in SwiftUI or is the UIKit example on the right not what you were looking for? Let me know,  Travis Trotto - DTS Engineer

Sorry for the delay, I didn't get the notification. Thanks for the code, I would recommend to add a link to a focused project where I can download and play with it as of course without the images nor drop targets is hard to see what you are trying to accomplish and will help many developers here figure it out. Customize the drag preview to make the interaction more intuitive. You can modify the draggable modifier .draggable(player, preview: { VStack { Image(jersey) .resizable() .frame(width: 50, height: 50) if let player = content.player { Text(player.last) .font(.caption) } } }) Currently, the drop handler just prints the item. You might want to update the CellContent's player based on the drop? .dropDestination(for: String.self) { items, location in if let firstItem = items.first { print(Dropped: (firstItem)) // Update player logic here if needed // e.g., content.player = updatedPlayerBasedOn(firstItem) } return true } Looking forward to your focused sample. That'll help us better understand what's going on

Hi, The problems you are facing is due to the fact that you named your project SwiftUI. This is causing the build system to create a module for your app called SwiftUI which is the exact same module name that the system library is called. I expect you'd see these issues resolved if you rename your app to something that doesn't match one of the system frameworks.

Apologies for the delay! Please see our doc main page: https://developer.apple.com/documentation/foundationmodels The Foundation Models framework provides access to Apple’s on-device large language model that powers Apple Intelligence to help you perform intelligent tasks specific to your use case. This article from Apple says something similar: https://machinelearning.apple.com/research/apple-foundation-models-2025-updates The new Foundation Models framework gives access to developers to start creating their own reliable, production-quality generative AI features with the ~3B parameter on-device language model.

There is however a problem with this solution. If there is a TextField in the popover, typing in makes it firstResponder ; and the parent window controller do not receive mouseEnter events that triggers the tooltips. Which means I do not need to simulate mouseDown but just makeFirstResponder. So at the end, the question boils down to: how to manage the conflict between popover and its parent window about FirstResponder. Is it possible to have first and second responder, I mean forwarding the mouse messages to the parent ? Considering that The shared NSApplication object performs the important task of receiving events from the window server and distributing them to the proper NSResponder objects. NSApp translates an event into an NSEvent object, then forwards the event object to the affected NSWindow object. All keyboard and mouse events go directly to the NSWindow object associated with the event. … When a window object receives an NSEvent object from NSApp, it distributes it to the objects in its vi

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. You wrote: To get info about nearby WIFi networks and filter out company specific SSIDs and to prioritize them Can you expand on that? What are you doing with that SSID list once you get it? It’s hard for me to suggest a path forward without a better understanding of your ultimate goal. [quote='875214022, arnair, /thread/808341?answerId=875214022#875214022, /profile/arnair'] Is there an official deprecation schedule or timeline? [/quote] No. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I can confirm there is something crashing my Apps that only have Launchscreen storyboards. I use Autoresizing and not Autolayout. And guys please, make a real effort to build a Launchscreen component in SwiftUI. It makes no sense in 2026, always ten years after and we still have a storyboard file messing/crashing our Apps in Swift.

Do this: Launch Xcode 26.3rc. File > New > Project. At the top, select iOS. In the main list, select App Playground. Complete the workflow from there. Good luck with your submission! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com