Replace socket-based Client->File Provider Extension communication with in-built File Provider XPC #6235
Labels
enhancement
enhancement of a already implemented feature/code
feature: 💽 virtual filesystem
os: 🍎 macOS
How to use GitHub
Feature description
Unfortunately our socket implementation at the moment treats the client-side as a communication receiver and the file provider extensions and senders. We initiate communication from the extension side and cannot do it the other way around
A better solution all around is to use the FIle provider's officially supported XPC based connection method to communicate between the extensions and the client
The text was updated successfully, but these errors were encountered: