Hi there, we also run into this issue, and this thread was a great starting point to begin the investigation and look for workarounds! Since no one brought this up, I'd like to share another workaround that reverts the behavior for the entire app, according to my findings. It's the NSViewUsesAutomaticLayerBackingStores user defaults flag. When set to false, everything gets back to normal. I prefer a solution that would be constrained to particular views where I do custom drawing. The problem is that the workaround presented here only works for a flat backing layer. I haven't managed to make it work with the NSScrollView architecture. For more details on my research, see this gist extracted from our internal documentation: https://gist.github.com/lukaskubanek/9a61ac71dc0db8bb04db2028f2635779 Do you have any idea or hints on how to make the workaround work with NSScrollView? Lukas

Hi, I came up with a solution based on the code signing certificate check. According to my early tests, it works reliable. Can you confirm?

I’m running into a similar issue with SwiftUI views presented in sheets not properly deinitializing instances of associated properties. Just tested your snippet with Xcode 15 RC and the DeinitPrinter doesn’t execute its deinit regardless of the detents configuration. In fact, it shows the same faulty behavior even without specifying any detents and using a standard full-size sheet. I’m still investigating, but I wanted to ask whether you can confirm this behavior and whether you’ve found a fix or a workaround. Also, have you filed a feedback?

The issue seems to be resolved on iOS 17.2! See this thread on Stack Overflow.

os.log types seem to be annotated as Sendable starting with Xcode 16 β3.