SwiftUI List performance

Follow-up / Update Update: New rejection – “Unlock Pro not responsive” on iPad, cannot reproduce locally I wanted to provide an update, as the app was rejected again after addressing the previous feedback. New rejection details Apple now reports the following issue: Guideline 2.1 – Performance – App Completeness Bug description: “Unlock Pro is not responsive” Steps to reproduce (per review): Tap “Unlock Pro” No action occurs Review device: iPad Air (5th generation) OS: iPadOS 26.2.1 This is confusing because: The app works correctly on my devices I tested the full purchase flow successfully: on physical iPhone in the iOS Simulator even on an iPad simulator The StoreKit purchase sheet appears as expected when tapping “Unlock Pro” I followed Apple’s advice to: uninstall previous versions reinstall fresh test upgrade paths I still cannot reproduce a state where tapping “Unlock Pro” does nothing. Important technical detail (possible cause) Looking closer at my implementation, I realized there is a silent

Hello Andrea_iOS, Can you please replicate this issue with just the relevant code in a small test project? If so, please share a link to your test project. That'll help us better understand what's going on, and troubleshoot the issue. If you're not familiar with preparing a test project, take a look at Creating a test project. Can you also please specify if your app is a SwiftUI app, or UIKit? Since this seems to result in visual glitches, you can also record footage of it in the iOS simulator or on a device, and attach it to a bug report in Feedback Assistant. Bug Reporting: How and Why? has tips on creating bug reports. If you create a bug report, please post the FB number here so we can track it. Thanks! Thank you for your patience, Richard Yeh  Developer Technical Support

I am jumping in late to this discussion, and I am ignoring a couple details at this point until can I re-read a few times, but I did experience the same issue when attempting to attach a sheet to Buttons inside a List. It was about the same behaviour, with the sheet closing the first time it was opened, then it behaved reliably afterward. I spent time looking into making sure the items had a stable identity, but never found a way around the issue. I don't like the usage as much, but I ended up just moving the sheet outside the custom component and above the List, and everything is working as expected now. I was thinking there was something going on with 2-way binding and race conditions, and maybe something being managed based on animation completions (imagining something in a bridging layer to UIKit), but didn't dig into the thought too much. Also, I still know much more about React and other reactive JS setups than SwiftUI, though that's trending in the right direction. As a side

Sorry for the confusion, and you assumed correctly that copying in the Finder works, but I actually meant something else. What I meant was this: a user of my app reported that when my app copies files from a QNAP NAS to a folder on their Mac, they get the error Result too large. When the app copies the same files from the Desktop folder, it works. Copying the files with the Finder, regardless their source location, works as well. From what the user told me, the issue only happens with some files. I actually asked them to narrow the issue down as much as possible and they found a folder with a single file, and copying that folder always causes that error. Interestingly, the destination file is actually created but has a much smaller size than the source: 250 KB instead of 34 MB. The user also shared that file as a zip archive on Dropbox with me. I ran the ls -l@ command on it to see its extended attributes and their size, the output was: com.apple.FinderInfo 32 com.apple.ResourceFork 286 com.apple.quarantine 5

Thanks for the post, trying to see what you are describing, running into a simulator 26.2 and I don't see what you are describing, can you provide images or screen recordings showing the experience so SwiftUI experts can jump in and help? Albert Pascual
  Worldwide Developer Relations.

It sounds like you're aware of what a routing app is, but just to confirm details: A routing app provides navigational directions between two locations. It is enabled inside of an Xcode project by going to the Capabilities tab, and adding the Maps capability, which will then show you a list of checkboxes for the transportation modes by which you're able to provide navigational directions between points. Those checkboxes correspond to values added to your Info.plist file under a key named MKDirectionsApplicationSupportedModes. It sounds like you're not providing directions, but you should check to make sure the above capability isn't enabled accidentally. And if you're not providing directions, also don't enable this capability just to try and solve this error, as I've seen people get tangled up further by trying that. If all of that looks good and that capability wasn't accidentally enabled, then the next thing you should do is to open a bug report with the details of your App ID and the build number

[quote='874071022, ball-hayden, /thread/807938?answerId=874071022#874071022, /profile/ball-hayden'] It's interesting that your guide says DevForums is not an official support channel, [/quote] That confusion is my fault, alas. Historically, DTS provided two forms of support: Formal support via technical support incidents Informal support, via the forums, mailing lists, and so on In 2024 we changed that process, putting a lot more emphasis on the forums. That way the results of our work are available to the entire developer community. As part of that we renamed technical support incidents to code-level support requests. Quinn’s Top Ten DevForums Tips was written before the 2024 change, meaning it originally used the old language. I tweaked the text slightly when that change rolled out, but re-reading it today it’s obvious that it wasn’t sufficiently clear. I’ve just updated the post to improve this. [quote='874071022, ball-hayden, /thread/807938?answerId=874071022#874071022, /profile/ball-hayden'] It

import SwiftUI struct DocumentTemplatesView: View { @StateObject private var documentService = DocumentService.shared @State private var selectedCategory: DocumentCategory? @State private var selectedTemplate: DocumentTemplate? @State private var searchText = var body: some View { NavigationView { VStack(spacing: 0) { // Search Bar HStack { Image(systemName: magnifyingglass) .foregroundColor(.secondary) TextField(搜索模板, text: $searchText) if !searchText.isEmpty { Button(action: { searchText = }) { Image(systemName: xmark.circle.fill) .foregroundColor(.secondary) } } } .padding() .background(Color(.systemBackground)) // Templates List if documentService.isLoading && documentService.categories.isEmpty { ProgressView(加载中...) .frame(maxWidth: .infinity, maxHeight: .infinity) } else if documentService.categories.isEmpty { VStack(spacing: 20) { Image(systemName: doc.text) .font(.system(size: 60)) .foregroundColor(.gray) Text(暂无文书模板) .font(.headline) .foregroundColor(.gray) Button(重新加载) {

[quote='814079021, sdavda, /thread/814079, /profile/sdavda'] the Network Extension process is suspended [/quote] This comment suggests that you have misunderstood how sleep works on our platforms. When the system sleeps, the main CPU [1] stops running, meaning that all code on the device stops executing [2]. Now, on iOS and its child platforms we will suspend an app’s process when the app moves to the background. That mechanism is completely different from system sleep, and it doesn’t exist on macOS. [quote='814079021, sdavda, /thread/814079, /profile/sdavda'] Is it possible to suppress the sleep and wake callback methods of NETransparentProxyProvider when the device is performing a maintenance/Dark Wake … ? [/quote] Not directly. [quote='814079021, sdavda, /thread/814079, /profile/sdavda'] Is it possible to prevent the NETransparentProxyProvider process from being suspended during sleep … ? [/quote] That question doesn’t make sense given the design that I’ve outlined above. [quote='814079021, sdavda

You can’t scroll to an item added in the same update; by the time you call scrollTo, the system don’t know about the new item. The right way to do this is to use onChange so that SwiftUI enqueues a new update once the collection has propagated through. Like so: struct ContentView: View { @State private var items = Array(0 ..< 20) var body: some View { NavigationStack { ScrollViewReader { proxy in List { ForEach(items, id: .self) { item in Text(Row (item)) .onTapGesture { proxy.scrollTo(item, anchor: .bottom) } } } .toolbar { Button { let newItem = items.count items.append(newItem) } label: { Image(systemName: plus) } } .onChange(of: items.count) { proxy.scrollTo(items.count-1, anchor: .bottom) } } } } } Let me know if this helps, and if you have any further questions please share a sample code that reproduces the issue. That'll be helpful in getting more context.

The files, both user-selected and sidecar, reside in a folder inside my user’s document folder, and I try to read the sidecar when the user opens the audio file. OK. SO, one thing I would test here is what happens if you test the same code with files that are in a directory outside of the normal user hierarchy. You can try with a directory inside your home directory, but I actually suggest using a folder ENTIRELY outside the user hierarchy— for example, on a disk image or an external volume. The issue here is that macOS has multiple independent systems of data protection, most of which are focused on user data (like the contents of ~/Documents/). Moving outside of that hierarchy means you’re looking at the basic case, which is easier to evaluate. Looking at the other cases here: I can access the sidecar file from the terminal and load its content. FYI, Terminal.app is a tricky tool to test an experiment with. The issues here are: It's not sandboxed, which exempts it from the more aggressive file protection yo