Now, I have created an extension via the fileprovider template and adopts fileprovider protocols. But when i download a file, the system throws the error: "Couldn't communicate with helper application". From the system log i can see that the fetch-content failed with such error: ┳139b4 ‼️ done executing <FP2 ‼️ fetch-content(a file 1) why:materialization|itemChangedRemotely sched:userInitiated.1647482996.810533#1647482996.810533 error:<NSError: Cocoa 4101 "Couldn't communicate with helper application." Underlying={NSError: POSIX 2 "couldn't issue sandbox extension com.apple.app-sandbox.read-write for '/f/db641e9a04e144c6b320': No such file or directory" }}>> Any advise would be appreciated, thanks!

Hello, everyone, I'm trying to upload a symbolic link file's contents through file provider. The contents in createItem is empty when the file is a symbolic link, so it needs to be uploaded according to the symlinkTargetPath in item, but I can't get the contenst according to the symlinkTargetPath. For example, if I use ln - s test.md test.link creates a symbolic link, the symlinkTargetPath will only contain test.md. If I use ln - s aaa/test.md test.link creates a symbolic link, the symlinkTargetPath will only contain aaa/test.md , there is no specific path to the file. So how can I get the contents of the symbolic link file ?

Hello, everyone. I am using fileprovder to update the file on the server to the local, but when my local file is opened by another application (such as misrosoft word), fileprovder will notify the file has been updated on the server through enumerateChangesForObserver, and then fileprovider will get the file's latest content from the server. But after getting the file, the icon of the file has always been a cloud icon, and has not become a materialized state. Is there any way to catch this error or recover from this state? Thanks!

Hello everyone, I am developing an application based on File Provider. Now I want to interact with the user when they open the directory. For example, when a user opens a directory, an alert message is displayed to interact with the user. So, I can prompt the user to enter the password before they can access this directory. NSFileProviderUserInteractions seems to only restrict certain operations on files, such as copy or move, but no open. Thanks a lot.

When upgrading to macOS 14.5, the FileProvider extension is consistently restarted by the system. This issue was not encountered with macOS 14.0, where the FileProvider extension typically remained uninterrupted. Additionally, I observed that when adding multiple domains using the same process, only one FileProvider extension would operate in 14.0, whereas in 14.5, a separate extension runs for each domain. I haven't found any release notes mentioning this change. Is this behavior intended? I also have filled a feedback FB13810567.