SwiftUI List performance

[quote='876600022, anosidium, /thread/815819?answerId=876600022#876600022, /profile/anosidium'] You advised that I should enable all the settings. [/quote] Well, yes, if you read that one sentence in isolation. However, I made it clear that one specific setting, Enable Soft Mode for Memory Tagging, reduces security, so if you goal is security then enabling that is probably not a good choice (-: [quote='876600022, anosidium, /thread/815819?answerId=876600022#876600022, /profile/anosidium'] I am therefore inclined not to enable it. [/quote] Or you could profile your app and see if it makes a difference in pratice. That’s generally the best way to approach performance trade-offs. [quote='876600022, anosidium, /thread/815819?answerId=876600022#876600022, /profile/anosidium'] I am not entirely sure what is meant by logging in [Soft Mode] [/quote] Quoting Enabling enhanced security for your app: This entitlement makes hardware memory tagging operate in soft mode, where the system produces a simulated crash

Additional info: I have confirmed that users can successfully revert from the downgrade to the original product via the iOS Settings app (Settings > Apple ID > Subscriptions). The issue seems to be specific to performing this action within the app using the StoreKit 2 API.

Hello, I would like to get more information. What error do you see when you try and log into https://account.apple.com or https://business.apple.com When it states the account is locked, steps to be taken are listed in the same pop-up.  Travis Trotto - DTS Engineer

Thank you for sharing the post and the partial code. I suggest posting the code starting from the Toolbar instead of providing only a ToolbarItem. Hope other SwiftUI gurus here can jump into this thread as my SwiftUI skills are not as good as others for sure!! Looking at your item it seems like you are setting the frame to 20x20? I think by default in SwiftUI only registers taps within the bounds of its content. Taps on the surrounding padding or button area are ignored. To ensure taps anywhere within the trigger the action, we can use a to expand the tappable area, see your frame? The modifier ensures that taps anywhere within the defined shape are recognized. // Removing the Toolbar too :-) ToolbarItem(placement: .navigationBarTrailing) { // guessing on toggleBookmark :-) Button(action: toggleBookmark) { ZStack { Circle() .foregroundColor(.clear) .frame(width: 54, height: 54) // Adjust size as needed Image(systemName: isBookmarked ? bookmark.fill : bookmark) .resizable() .aspectRa

Thanks @DTS Engineer, I have already read that documentation. You advised that I should enable all the settings. However, I noticed that for Memory Tag Pure Data, the description states that “it may incur a performance overhead”. I am therefore inclined not to enable it. Regarding Enable Soft Mode for Memory Tagging, the description states that “memory tagging faults will not crash and will be logged instead”. I am inclined to leave this disabled, as I would prefer the application to crash so that I can receive a crash report and potentially fix the issue. I am not entirely sure what is meant by logging in this context, would this appear in the Xcode console when running in Debug mode? As you are knowledgeable about AppKit and Mac computers, may I ask if you would mind looking at my other post about StoreKit 2? I am at my wits’ end, as I would like to ship the Cocoa app using the API but cannot because it is not behaving as expected. I am tempted to submit a code-level support request for this.

Upskill in SwiftUI and system design, explore leadership roles, diversify platform expertise strategically.

That's interesting about the difference between NSOperation and NSThread as far as Mach ports go. I watched the # ports in Activity Monitor as I ran a job, and it certainly doesn't climb as each job runs. It goes from initially in the 300s to the low 500s right when the job starts, and stays around there, even after the job ends, and then I run the same job 2 or 3 more times without quitting. Well, that's the joy of Mach port leaks... you never REALLY know what you'll get. So, as some broader background here, the actual issue here isn't really about the thread API itself- ultimately, both APIs are using pthreads and the special pthread GCD uses aren't really different than standard pthreads. The real issue here is that you don't actually own the thread and the assumptions AppleEvents/ScriptingBridge were built around. Both of those APIs predate GCD (by many, many years) and are built around the assumption that they'll be used on a long-running thread that's running its own runloop, as that was basically THE p

Thanks for this awesome post. Yes, low power will trigger the device to go night night if possible. This is a great post for other developers to provide tips and ticks how to keep the device awake on a recording session. https://developer.apple.com/documentation/uikit/uiapplication/isidletimerdisabled Your approach of setting is indeed the standard way to achieve this. However, certain power management features, like Adaptive Power Mode, can override these settings, as you've observed. Ensure that you have an active configured while recording. This typically helps in signaling to the system that media capture is in progress, which should naturally prevent the device from sleeping. Unfortunately, iOS doesn't provide public APIs to directly detect Adaptive Power Mode specifically. However, you can check for Low Power Mode . While this doesn't exactly map to Adaptive Power Mode, it can still be useful for alerting users. Since detecting Adaptive Power Mode isn't directly possible, consider displaying a message w