DTiPhoneSimulatorErrorDomain Code 2

I see, thank you for pointing this out. So it is not a percentage, but an actual number of pages. Could you expand a little on how to interpret in your previous answer? So, stepping back for a moment, the basic issue here is deciding when should the kernel stop just blindly backing memory. It COULD (and, historically, did) just limit that to total available storage; however, in practice, that just means the machine grinds itself into a useless state without actually failing. So, what macOS does is artificially limit the VM system to ensure that the machine remains always in a functional state. The next question then becomes how to implement that limit. There are lots of places you COULD limit the VM system, but the problem is that the VM system is complicated enough that many obvious metrics don't really work. For example, purgable memory[1] means that simply dirty pages doesn't necessarily work“ - a process could have a very large number of dirty pages, but if they're all purgable, they shouldn't really coun

The following code segments run when building and running the app, or after going home and re-opening the app, but now when quitting the app and re-opening it again. What code can do that? Please be more precise in explaining the use case and what they mean exactly after going home and re-opening: what do you do exactly when you quit: what do you do precisely ? What do you get ? What did you expect ? explain what you get printed for each of the cases. Note: you should have more discriminant print: init() { print(init test) } .onAppear { print(onAppear test) } .onChange(of: scenePhase) { _, newValue in print(onChange (newValue)) }

Thank you for the post and providing detailed information. I am curious about how you are handling Live Activity events in code as you didn’t provide any focused sample. I recommend reviewing our samples to see how it works well to dismiss Live Activities. Handling Live Activities with AlarmKit and ensuring they behave correctly with the Dynamic Island can be tricky, especially concerning state management and user interactions. Make sure that when your app dismisses the Live Activity, it explicitly ends the activity using the APIs. Before dismissing, ensure the Live Activity’s state is updated to reflect that it is no longer active or relevant. Ensure that your logic for starting a Live Activity does not inadvertently create multiple instances. Use unique identifiers and conditions to check if an activity for a particular alarm is already running before starting a new one. As an interim measure, clearly communicate to users the intended method to dismiss Live Activities (using the X button) through U

Welcome to the forum. Is it just a warning or does it stop compiling and build ? If just a warning, you can ignore. There are 2 libraries that propose the same function. You may however try a clean build folder (Product menu) to clean derived data. If you are in debug mode, change to release mode, to see what happens. To change mode: Edit Scheme…

The hashing logic you showed look correct, the only thing I would double check is all numbers must be 32-bits. The next sample app/server project will be published fairly soon which includes code and tools that will help you work with the Bloom filter bit.

How are you cloning these VMs? Specifically, are you calling Virtualization framework from your own code? Or is your infrastructure relying on VM infrastructure provided by another third party? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[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.

The general model for apply(_:completionHandler:), as explained in the docs, involves three steps: Apply the Wi-Fi configuration. Join the network. Bring up the TCP/IP stack on that interface. Problems with step 1 are delivered to your app via the method’s completion handler. Problems with step 2 are communicated to the user via an alert. Problems with step 3 can result in a variety of different behaviours. If you’re seeing a case where the devices fails to join the network and that’s not reported to the app or the user, that’s something we should investigate via a bug report. See this post for my advice on filing Wi-Fi bugs. If you do file any bugs about this, please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com