Fileprovider Recycle Bin recovery does not trigger the create event, and dataless files should not be moved to the Recycle Bin

Question

EastonLi OP

Created 3w

Replies 5

Boosts 0

Participants 3

I want to use FileProvder to implement the function of recovering from the recycle bin (the cloud recycle bin does not move, and after the local recycle bin is restored, the upload event is triggered again), but testing shows that the current recovery from the recycle bin is through the modifyItem event, and the CreateItem event is not triggered again to upload locally restored files
Implement the deletion of undelivered files (dateless) without moving them to the recycle bin, which currently appears to be achieved by granting file. dash permission. But it is possible for the content of a file to be manually verified by the user. How can this be solved? How can we dynamically monitor whether a file is dataless

Thank you for your reply. Could you please help answer my question

Answered by mikra in 868178022

Just to check if a file under a given URL is dataless or not, you can have a look at URLUbiquitousItemDownloadingStatus.

Whether you can use this inside File Provider extension process or not, or how to know which URLs to check - that's a separate question I can't answer.

Boost

Answer 1

EastonLi OP

2w

someone help me，thanks

0

Answer 2

EastonLi OP

2w

Is anyone there? Can you help me！ thank you

0

Answer 3

mikra OP

1w

Accepted Answer

Just to check if a file under a given URL is dataless or not, you can have a look at URLUbiquitousItemDownloadingStatus.

Whether you can use this inside File Provider extension process or not, or how to know which URLs to check - that's a separate question I can't answer.

0

Answer 4

Engineer OP

Apple

6d

You can use -[NSFileProviderDomain supportsSyncingTrash] to tell the system that the domain does not support syncing the trash. When configured this way, the system will handle trashing of downloaded and dataless files appropriately on your behalf.

0

Answer 5

EastonLi OP

5h

I am currently encountering a problem: during the process of uploading a large file, I have moved the file that was not successfully uploaded to the trash can. These two operations have been tested to be serial (triggering the 'create Item' callback first, followed by the 'modify Item' callback), which means that the file must be uploaded before it can be moved to the recycle bin (which can also result in the file being stored in the cloud recycle bin). I want to implement: directly interrupt this upload process and then do not complete the upload. How can I achieve this? Please help me. Thank you

0