I hit the same problem as the OP (and I'm considering posting my code as open source in a bit). While editing text fields embedded in a List, the background turns white behind the text field (unexpected and unfortunate, when the background of my list and the text fields are a color other than white). But to get OP to jump over the problem, add this: extension NSTextView { open override var frame: CGRect { didSet { backgroundColor = .clear drawsBackground = true } } } The problem with adding this to your SwiftUI code is that it will set the backgroundColor to clear for ALL other AppKit NSTextViews. You can't set a private access modifier on this extension which has an open var. So this problem is still an open issue for me. edit: I'm wondering if the OP has the same application setup as me -- where I am embedding a SwiftUI view via a NSHostingView inside a regular NSWindow alongside other (non-SwiftUI) NSViews. When it's a pure SwiftUI app, I do not see this problem when editing text fields.

Getting closer to working. I got cloud signing permissions enabled on my team account, plus I can now create certificate/profiles (which I couldn't do before). The main app (first built years ago) uses an old application identifier prefix that's separate/different from the team identifier. But the "Register an App ID" screen in my developer account has a dropdown that shows all possible app prefixes, not just the team ID. Nice! So now old main app A and brand new demo app B both have matching prefixes and a keychain-access-group of something like RR3K76LW2Q.com.myke.shareditems. Even after fully deleting the previous demo app from before and reinstalling a new app with a manual provisioning profile (the "iOS App Development" radio button was selected when registering the new profile)) , I'm still getting -34018 errors when trying to fetch the shared items.