SwiftUI List performance

I know this is years later.. but I am going through a reverse situation. I have falsified everything for iPad in the code, am not required upload iPad photos, but the reviewers keep being told to judge how my app performs on iPad for some reason. So frustrating. And only a small number actually read the messages before reviewing, so I am stuck in a loop with the reviewers of them thinking the app is for ipad when it is not. Hopefully, I can get some help with resolving this soon.

Hi, we have an open feedback listing that we are still awaiting a response for FB21147185. Is there any update on this?

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. I am aware of this requirement Cool. Is it ok if I just demo it with the countdown timer in one part I’m not deeply involved in how entries are judged, so I can’t give you a definitive answer to this. Rather, I want to address the technical side of it. iOS has strict rules for both security and background execution: On the security front, the general rule is that app A can’t see what app B is doing [1]. On the background execution front, the general rule is that an app can’t run indefinitely in the background. A naïve implementation of your app might run something like this: User launches and configures your app. Your app runs in the background looking at user activity. If your app sees that the user has been continuously using apps for a long time, it posts a notification reminding them to take a break. This approach would work on the Mac [2], but it will not work on iOS. Now, that doe

We've struggled to reliably support our FPE on iOS since the beginning due to this limitation. We desperately need more memory in order to provide the level of quality and performance expected by our shared users. Feedback submitted: FB21678908

Hi Kevin, Thank you for your deep insight. Your theory matches our observed facts perfectly! I have just updated FB21636775 with the latest symbolicated crash log captured today (Jan 19). 1. Evidence of Concurrent Execution Conflict From the symbolicated backtrace, it is clear that at the moment of the crash: Thread 1 (AuxiliaryQueue): Is in the middle of executing UserCreateTargetForID (Frame 12). This RPC call has not yet returned to our DEXT. Thread 4 (Crashed Thread): Has already received the hardware interrupt for the first command (TEST UNIT READY) and is attempting to invoke the completion API. 2. Crash Characteristic Analysis The system encountered an Address size fault (Null dereference) at address 0x0000000000000008. This confirms your deduction: because UserCreateTargetForID is still pending on the AuxiliaryQueue and has not returned, the target-related objects or OSAction metadata in the kernel are not yet fully initialized. Attempting to invoke the action from an asynchronous thread leads to inva

Problem: Misaligned Vision Bounding Boxes in SwiftUI When using AVCaptureVideoPreviewLayer inside a UIViewRepresentable, my Vision bounding boxes were either stretched, offset to the side, or shrunken in the center. The standard GeometryReader approach failed because it reported the full screen dimensions, while the camera feed was being letterboxed or aspect-filled. The Solution: Native Layout Bridging I moved away from artificial scaling factors (like 1.33 or manual multipliers) and implemented a Pure Natural layout bridge. Capturing the Real Video Frame I added a closure (onLayout) to my UIView subclass. This allowed the UIKit layer to report its actual non-zero dimensions (e.g., 832×420) back to SwiftUI only after the layout math was finalized by the system. This eliminated the (0,0) size errors during initialization. Standardizing the Vision Request I set the VNImageCropAndScaleOption to .scaleFill. This ensures that the Vision coordinate system (0.0 to 1.0) maps exactly to the edges of

Is it safe and supported to move Xcode to an external hard drive (SSD), use it from there, and simply connect the drive whenever I need to work with Xcode? Yes. Absolutely. Are there known issues with performance, stability, or updates? Nope. Apps can run from any visible location. Are there components that must remain on the internal disk to avoid unexpected behavior? Nope. Xcode is self-contained. Is this a reasonable long-term setup, or just a temporary workaround? Neither. It can't possibly work. The Xcode app itself is quite small. Moving it will do absolutely nothing to solve any storage problems. The problem with Xcode is the Developer folder. On my computer that's 34 GB for Developer in my home folder. There's another one in Library that's 80 GB. And in the System Library folder, there's an iOS Runtime folder for another 211 GB. And this isn't even my primary development machine. This is my backup and test rig. You need a minimum 1 TB boot drive for Xcode. Sorry.

@petriniemela Welcome to the forum. How do you see your app is not distributed ? It does not appear on the AppStore ? Have you checked that you have set the countries for distribution properly (is Finland in your list) ? You answered in the comments (better to answer with a reply, more visible). Ready for distribution is the last stage, no need for more. Did you receive a mail notification ? If you still have issue, the best is to contact support. https://developer.apple.com/contact/ If you want someone else to check, could you give the name of your app ? Note: avoid duplicating posts.

I am afraid your statement is quite confusing. You first talked about what happened in 2012. You talked about it again in the middle. You talk about whatever happened in 2019. You then talk about having purchased iPhone 17. Yet, I can hardly tell where you are having difficulty. Are you having difficulty creating an Apple ID? Or are you having difficulty enrolling yourself in the developer program? If it's the former, this isn't the right place to ask your question as Apple people often explain that this place is intended for software developers. If it's the latter, where does your iPhone 17 come into play? As long as I watch the YouTube video titled 'How to Enroll in Apple Developer Program (Step-by-Step)' with a British accent, I don't see the button you refer to as 'the registration button.' The following is a list of buttons I see in the video. Start your enrollment Continue Purchase Meanwhile, I had to create several new Apple accounts in order to test a new iPhone app that uses iCloud accounts

Is it realistic to expect App Store review approval when requesting Full Disk Access? Under what conditions or use cases is such permission typically accepted by Apple? You haven't really said how you intend to implement what you call 'Full Disk Access.' I currently have two desktop applications with the 'Full Disk Access' capability with read/write permissions. If that's what you are talking about, your application is allowed to have read and write permissions, as opposed to just 'read' if the application is designed to save files to the disk. So, again, Is it realistic to expect App Store review approval when requesting Full Disk Access? Under what conditions or use cases is such permission typically accepted by Apple? I would say 'Yes.' But reviewers are not predictable. I had one desktop application rejected by a reviewer 6 or 7 years ago. His or her reason was, as I recall, the application did not write files to the disk when in fact the application did use NSSavePanel to let the user save files to the d

Thank you for this solution, this is way simpler than what I was trying to do. For anyone who wants this behaviour for themselves, I have put the solution above in a small reusable AssetPackManager extension: import System import BackgroundAssets @available(iOS 26, macOS 26, tvOS 26, *) @available(watchOS, unavailable) extension AssetPackManager { /// Performs a shallow search of the specified directory within all asset packs and returns the paths of any contained items. /// - Parameter path: The relative path to the asset pack directory whose contents you want to enumerate. /// - Returns: A list of `URL` objects, that identify the contents of this asset pack folder /// - Throws: When the path isn’t relative or when some other error occurs while retrieving the folder content. public nonisolated func contentsOfPack(atPath path: String) throws -> [URL] { let url = try AssetPackManager.shared.url(for: FilePath(stringLiteral: path)) let itemsInDirectory = try FileManager.default.contentsOfDir