We are also facing same kind of problems. Is it possible to avoid listing our app in this login items? Or can we get some notification in case if user switched this button off so that we can ask user to be sure before doing this and its consequences?

Yes, I verified on macOS 11 beta 9 (mac mini 2014). Me too found same issue with images if we try to present in NSImageView. Looks like pixels are getting overlap as per my observation. But same look all good on macOS 10.15.

Reported Bug Id : 8736010

Can you please check Apple sample, it has some issues I guess for Safari? It has some problem with object passing to remoteNetwork (NWHostEndpoint). The sample code you have shared here, it's working. Not working from Apple sample: let filterRules = ["0.0.0.0", "::"].map { address -> NEFilterRule in       let localNetwork = NWHostEndpoint(hostname: address, port: FilterDataProvider.localPort)       let inboundNetworkRule = NENetworkRule(remoteNetwork: nil,                           remotePrefix: 0,                           localNetwork: localNetwork,                           localPrefix: 0,                           protocol: .TCP,                           direction: .inbound)       return NEFilterRule(networkRule: inboundNetworkRule, action: .filterData) } Working code shared by you: let anyHostAndPortRule = NENetworkRule(       remoteNetwork: NWHostEndpoint(hostname: "0.0.0.0", port: "0"),       remotePrefix: 0,       localNetwork: nil,       localPrefix: 0,       protocol: .TCP,       direction: .any ) let filterRule = NEFilterRule(networkRule: anyHostAndPortRule, action: .filterData) May be we should fix this in Apple sample too... Also in call back handleNewFlow, remoteEndpoint or localEndpoint getting nil for Safari due to which it is returning from guard let condition. It is all working fine for other browsers like Google Chrome and Firefox with Apple Sample...

I am already using the same configuration you mentioned. The handleNewFlow method is not getting called for Safari. It is working only for Firefox and Chrome. In that case, is it a bug in the API or something?

Here is bug id: https://feedbackassistant.apple.com/feedback/8332928

Got it thanks...I can see in Xcode 12, its showing as expected...

Its working thanks... I don't see any such information in Apple documentation. If this is work around solution for issue then what happen to already released apps when apple will fix this issue? If it is really an issue then apple should fix it asap or documentation should be updated accordingly.

Its working thanks... I don't see any such information in Apple documentation. If this is work around solution for issue then what happen to already released apps when apple will fix this issue? If it is really an issue then apple should fix it asap or documentation should be updated accordingly.

Hi, I am also facing same problem. Having issues with release provisioning profile and working fine with develop provisioning profile. Any update on this?

I am also facing the same problem. Any progress on this?