@DTS Engineer In this attached file, do we need to change anything, are any API's changed? WireguardFlutterPlugin.swift

@DTS Engineer Thank you for the clarification. Just to confirm: our current app is built using the legacy NetworkExtension framework and uses NEPacketTunnelProvider inside an .appex. We're distributing the app outside the Mac App Store via a .pkg installer and signing with Developer ID. We understand that the provisioning portal automatically adds the -systemextension suffix to entitlements, and your reply referenced TN3134, which appears to mandate System Extensions for direct distribution. Could you please confirm definitively: Is there any way to continue using the legacy Network Extension framework (i.e., .appex-based NE providers) outside the Mac App Store on macOS 14+? Or are we required to fully migrate our app to use System Extensions (SystemExtensions.framework) instead of legacy .appex NE providers when distributing via .pkg? If there's no workaround, we’ll proceed with migrating to System Extensions—but given the scope of such a change, we wanted to confirm directly.