It working on iOS 17.5 GA, thanks.

@eskimo: Thanks for the reply, and slightly similar issue seen with macOS 14.4.1 update and many customers are facing this. Need help on this.

Thanks @eskimo for acknowledging it, any update on the feedback will help as customers constantly asking for updates.

Thanks Matt/Quinn. We have been using AppProxyProvider as appex for some time now and as PerAppVPN mainly, it works fine on iOS and on macOS we get this alert. We will try using System Extension for macOS and see it it fix the issue.

No problem. In that case you could try the approach of: Return YES from handleNewFlow: and then immediately call closeReadWithError: and closeWriteWithError: on the flow. Thanks much Matt, it worked on Catalina (macOS 10.15.7). Having inherent issue on BigSur(macOS 11) with NETransparentProxyProvider and so couldn't try it on BigSur, will open DTS for this.

Hi Quinn, Please let us know if anything we can do for above, like using special entitlements. Thanks

Thanks Matt, Use NEAppProxyProvider instead of NETransparentProxyProvider. Couldn't get above completely, NETransparentProxyProvider extends NEAppProxyProvider and NETransparentProxyProvider available in macOS 11.0 (BigSur). We have extended NETransparentProxyManager in our TransparentProxy, and receiving flow at handleNewFlow: