I'm looking for instructions on how to set up XCode to debug a Preference Pane project in XCode 8.

I'm working on an AppKit-based macOS application that has a transparent pane as part of the window.  The view structure is an IB-based storyboard. The transparent pane has UI items embedded in it, one of which is an NSTableView (which also has a transparent background.  The cell view backgrounds are also transparent.  After the application launches, the Table View leaves graphic artifacts (in some background layer) when the table is scrolled. If the window is resized, the artifacts disappear (resizing seems to force a redraw).  If the table is then scrolled, the artifacts re-appear (again, at the last position of the actual objects). The artifacts appear to be grayscale outlines or the edges of the objects (text or images) This is only an issue when using transparency.   Does anyone know what these artifacts are from, or perhaps how to get rid of them?  I assume that there is some redraw/refresh operation that is not occurring when it should (and is an issue with transparent backgrounds), but I've not yet been able to figure out how to properly trigger it.   (macOS Monterey 12.0.1, Xcode 13.2)

Does anyone know of a way to build a macOS application in 100% SwiftUI with a transparent window background? I want to be able to place opaque SwiftUI views in front of the transparent window, so that a select portion of the window is transparent (or slightly blurred). I know how to do this with an AppKit storyboard-based application (with embedded SwiftUI views in NSHostingController containers). However, I've not found a way to get a transparent (or slightly blurred) window within a 100% SwiftUI-based application. Is this possible, or is the hybrid approach (AppKit storyboard + hosted SwiftUI views) the only solution?

What is the best practice for working (development of a new app that includes use of iCloud entitlement) with a client that already has a Developer Account, and has existing apps in the App Store? According to Apple's transfer criteria here, any app that uses the iCloud entitlement can not be transferred. "No version of the app can use an iCloud entitlement." Also... The App must have had at least one version that has been released to the App Store. ... so if this is a new app that has not yet been released to the App Store, this also seems like an impediment to an app transfer. Should one just request an invitation to join the client's Developer Account to gain Developer role access priviledges, and is that sufficient? Are there any other alternative (or better) strategies?

I'm attempting to debug the ActionRequestHandler in a Finder "Quick Action" extension, and appear to be running into timeout problems.I started with Apple's sample project for creating Finder "Quick Action" extensions. I'm able to load the extensions, and trigger the Xcode debugger via a Finder "Quick Action" popup menu. So far, so good... However, after halting in the extension's ActionRequestHandler in the Xcode debugger (as expected), and then stepping a few times, or hitting a couple of breakpoints, I get a Finder dialog with with the message: "Couldn't communicate with a helper application". The debugger halts in the extension with signal 9.I suspect that there is a timeout limit in the communication between the Finder and the extension, and the extension is killed if it takes too much time to respond (resulting in the Finder dialog message). Is there a debug setting somewhere where this timeout can be disabled or lengthened, so that it's possible to step through Finder extension code without running into this problem?