On MacOS 12.0 (Monterey), no attempt to use tccutil (with sudo or otherwise) works. All cases returned an error: mbp16inch2021:/ Stephen$ sudo tccutil reset com.mycompany.AppName tccutil: Failed to reset com.mycompany.App mbp16inch2021:/ Stephen$ tccutil reset AppName tccutil: Failed to reset AppName DTS confirmed it didn't work for them, too. I'm about to submit a bug, but maybe I have the syntax incorrect?

I noticing that Monterey defaults to the NSWindowToolbarStyleAutomatic / NSWindowToolbarStyleUnified toolbar style, which suppresses the "use Small Size" menu item and customization checkbox. So I've set the window to use NSWindowToolbarStyleExpanded. However, the toolbar will no longer change to a smaller icon size, as it did in MacOS 10.14, 10.15, and 11.0. I've tried to set the toolbar item sizing to "Automatic" for all of our toolbar icons, but that results in bad positioning in both Regular and Small Size mode -- the height is way too big. The native size of the icon .png files are 128 x 128. What's odd is that if I resize the window with the toolbar to be wider, the NSToolbarItems in the overflow area will be displayed in the toolbar are 128 x 128, where the rest of the toolbar icons get displayed as a 32 x 32 icon. The only way to get it to layout remotely correct is to make the NSToolbarItem to have an explicit minimum size of 24 x 24 and maximum size of 32 x 32. And that USED to allow "small size", but on Monterey, it no longer does. Anyone had any success with small size icons on Monterey?

Sometimes while drawing from my main thread I have error conditions that I need to relay to the user, and often need to get the user to interact (enter text, press a button, etc) -- and then CONTINUE from inside the main thread drawing process that was interrupted. However, the main thread doesn't like it when you try to draw while already drawing from within the main thread (I think it even throws an exception if you try). Is there a canonical approach to handling errors that occur during drawing that require more sophisticated error handling?

Something has happened to our users that are running MacOS Sonoma: our app's main window (NSView ) is no longer getting the NSResponder deleteBackward "bindable command" message when the user presses the DELETE key, and is connected to an Apple Extended Keyboard. (it DOES work on a laptop, however) Similarly, laptops that have updated to MacOS Sonoma no longer send the previously-accepted unicode key code for the FORWARD DELETE key: "\u007F". Both these keys worked PERFECTLY on all earlier versions of MacOS (Mojave 10.14 through Ventura 13.x). Any insights?