show when run

Thank you, this has been helpful! If you don't mind, could you collect one more piece of data for us? Add the following to your ~/.lldbinit: log enable gdb-remote packets --timestamp -f /tmp/log_packets.txt Like before, make sure Xcode is closed. Then, launch the app to experience the slow startup, stop the application, and attach /tmp/log_packets.txt to the bug reported you opened. Please make sure you only do the experiment once, so that the log doesn't contain more than one run. Thank you for assisting us!

There’s a lot to unpack here but I’m still grinding through the holiday backlog so I’m going to focus on the critical bits. First, don’t test stuff like this on your day-to-day development machine, because cached state can confuse you. Rather, run tests like this on a fresh Mac, one that’s never seen your app before. I generally do this in a VM, where I can restore to a fresh snapshot between each test. Second, there is a supported way for a sandboxed app to achieve this goal on modern systems [1], namely, via the CGEventTap mechanism. See CGPreflightListenEventAccess, CGRequestListenEventAccess, and CGEventTapCreate in . This relies on the Input Monitoring privilege, rather than the Accessibility privilege, and that’s available to sandboxed apps. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] macOS 10.15 and later, IIRC.

If you are having trouble with App Store Server Notifications, we recommend using the Get Notification History API in the App Store Server API, it will show what notifications were attempted, when, and why they failed.

[quote='811013021, pjfloyd, /thread/811013, /profile/pjfloyd'] On macOS I see an extra mutex. [/quote] That doesn’t surprise me, but that’s probably the result of my not understanding your setup properly. When I run your cond_timedwait_test.c code natively and set a breakpoint on pthread_mutex_lock, I hit that breakpoint a lot inside the dynamic linker and various loaded-by-default libraries. But I suspect that you’re doing stuff to avoid that, like statically linking the executable [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Not something we support in general but tools like this often have to stray from the supported path.

I see, thank you for pointing this out. So it is not a percantage, but an actual number of pages. Could you expand a little on how to interpret in your previous answer? How does one find the available range? What does it mean to overcommit pages? Ideally, I would try to get as close as possible to a memory overcommitment scenario, would this correspond to an infinite number of overcommitted pages? Is there a way to enter infinite in this parameter? Or there is a maximum number, which can change from machine to machine? If I am interpreting the directionality this parameter has to move towards to, in order to get the desired behaviour, I need to retrieve this number, not just compute it roughly via the known 4KB size of a page and the capacity of the disk. Say the maximum number is 1200 pages. From the documentation, I am supposed to boot in recovery mode, disable SIP, and then run sudo nvram boot-args=vm_compressor_limit=1200 and then restart to make the changes effective. Do I need to keep SIP disab

For general background on this, see TN3179 Understanding local network privacy. As to your specific scenario: What platform are you on? While the local network privacy implementation is very similar on macOS and iOS, there are important differences. As you concerned about Safari? Or about a web view running in your app? That difference is important because a web view running in your app is considered to be your app from the perspective of local network privacy. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='811084021, iceboy, /thread/811084, /profile/iceboy'] its value keeps changing and then switching back to the original [/quote] Can you expand on this? When does it change? Between different runs of your app? Or across OS upgrades? Or something else? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='810603021, AamirNezam, /thread/810603, /profile/AamirNezam'] we are facing an issue with the certificate validation [/quote] Can you provide more context here? Certificate validation is used in a lot of different places — Safair, networking APIs, code signing, push notifications, and so on — and so it’s not clear where I should route your question here on the Apple Developer Forums (or, indeed, whether it’d be better routed elsewhere, like Apple Support Community, run by Apple Support). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

We are seeing the same in a SwiftUI runtime. Completely new crash. What version are you running?