Yes, this was useful for debugging layout constraints, but their history is no longer shown automatically now. The only workaround I've found is to get the constraint's address while in the view debugger, resume then go into the memory debugger and look up its address. This works, but is several more steps now.

I just wasted 2 hrs reading the confusing docs and trying to get this built, only to run into this same error. As typical for the last decades, Apple keeps failing at gaming. This is precisely why Apple has never been, or ever will be, taken seriously in gaming.

Keeps crashing for me whenever I use a proxy app to capture network traffic. Annoying AF.

The buggy LLDB RPC server constantly crashes whenever I use a proxy app to capture network traffic. I guess this is what we're to expect from a $trillion company now? #sad

What's happening is that you're using NSAttributedString to get a rich text string from HTML; this causes the system to internally use the WebKit engine to parse the HTML, and during this processing causes to runloop to get run, which triggers other code leading to internal inconsistencies. Try and see if you can trigger the parsing before (or outside of) the code that alters the rows.

Again, another important piece of critically missing information goes unanswered by Apple. #noOverviewAvailable.

Can someone from Apple please provide us some guidance here?? None of this is documented anywhere, and there's several similar questions unanswered, because the documentation simply doesn't exist! #noOverviewAvailable

Question in a similar vein: if an app has installed and registered a Login Item (via SMAppService), when the application is updated (either manually or via AppStore), do the Login Items registered that are currently running processes get restarted with the newly installed update of the app's relevant executables? I can find no documentation that describes what happens or is required in the case of an application update.

Known issue of Mail randomly crashing when downloading message while an extension (any extension, even Apple's own sample extension) is enabled. http://www.openradar.me/FB12794488 (among others submitted to Apple)

Another is MailCore2 https://github.com/MailCore/mailcore2

This needs to be supported - it's quite pointless to have macOS support in a VM if it's going to end up neutered on its most basic functionality.

I will third, forth, fifth and however many times it needs to be said to have this (Apple logins) supported in a macOS VM. It's quite pointless to have macOS support in a VM if it ends up being neutered on its most basic functionality. I encourage Apple to re-read StarPlayr's comment as many times a day as humanly possible, because they hit the nail on the head - this should've "just work[ed]" from day 1.