I've just started using xpc_connection_set_peer_code_signing_requirement() and can happily report that it meets all of my needs in terms of validating who my XPC connection is really connected to. However there seems to have been a slight oversight in that the new error XPC_ERROR_PEER_CODE_SIGNING_REQUIREMENT has either not been made public, or is not available to Swift code for some reason. For example: if event === XPC_ERROR_CONNECTION_INVALID { // OK } else if event === XPC_ERROR_TERMINATION_IMMINENT { // OK } else if event === XPC_ERROR_CONNECTION_INTERRUPTED { // OK } else if event === XPC_ERROR_PEER_CODE_SIGNING_REQUIREMENT { // Error: Cannot find in scope }

Filed FB8968738, I'll post here again if anything comes of it.

I am having the same issue. iOS devices work fine, but macOS devices won't connect to the development push service. Bug report: FB8968738

So I read through TN2265: Troubleshooting Push Notifications - https://developer.apple.com/library/archive/technotes/tn2265/_index.html#//apple_ref/doc/uid/DTS40010376-CH1-TNTAG24 and it looks like the problem is that APSD never connects to the *development* iCloud environment on macOS because: I get neither the success nor the failure delegate callback when registering for remote notifications apsctl status shows: daemon status:																Running certificate status:													 Provisioned, using existing certificate app refresh activity:												 Yes connection environment:											 development 	 courier status:														Not connected because there are no eligible topics 			enabled:																Yes 			stream connected:											 No 			connected to service:									 No I'm guessing "there are no eligible topics" means "you are not running any apps that connect to the development environment", so perhaps the problem is that it's not noticing that I'm launching my app that wants the dev environment? I'm kinda stuck at this point though because I don't see any documentation on apsctl that would allow me to troubleshoot further.

I submitted a feedback request to have this added, because right now there doesn't seem to be a way to make Form() containing TextField() look right on macOS because of the missing labels. FB8636648. I suggest you submit a feedback request as well.

Sorry, here is an example. Paste this into a new macOS swiftUI project and do a live preview to see what I mean. import SwiftUI struct ContentView: View {     @State var isPopped = false     var body: some View {         Button("Popover") {             isPopped = true         }         .popover(isPresented: $isPopped, content: {             MyPopover()         })         .padding()     } } struct MyPopover: View {     @State var moreControls = false     var body: some View {         Form {             Text("Text")             Button("Toggle") {                 withAnimation {                     moreControls.toggle()                 }             }             if moreControls {                 Text("More Controls")             }         }         .padding()     } }

I noticed the same issue in an ObjC app that has no swift (or swiftUI) at all so I don't think that's related. Xcode 12.2 beta, iOS/iPadOS 14.0

Using a file with 0700 permissions seems like the best I can do then. Thanks! That fits more easily into my existing design than adding a special install mode to the daemon.