Disable duplicate option in FileProvider extension
up vote
0
down vote
favorite
As the title says, I'm writing a Files app extension. In this extension the users access to some nodes will be restricted. So for example the user may only have read and create permissions on a node, meaning he can't delete anything inside that node. Therefore the move and delete options should be grayed out.
To implement this i dynamically define NSFileProviderItemCapabilities for every NSFileProviderItem based on the underlying permissions concept.
This worked for every option except the duplicate option, which seems to be enabled no matter what capabilities i assign/ not assign.
Since the user does not have create permissions on the node, the user naturally cannot create a duplicate in this location. The closest NSFileProviderItemCapabilities I found was .allowsAddingSubItems .
Example: We are in the node named "read" (the user has only read permissions for this room) therefore the NSFileProviderItemCapabilities of this room is only .allowsContentEnumerating . "read" contains a Folder "Random" which also only has the .allowsContentEnumerating capability. Since the .allowsDeleting capability is not set the delete option is grayed out and likewise since the .allowsReparenting capability is not set the move option is grayed out.
.
However the .allowsAddingSubItems capability is not set and still the duplicate option is enabled.
The apple documentation really doesn't help a lot here: https://developer.apple.com/documentation/fileprovider/nsfileproviderextension/providing_support_for_user-driven_actions doesn't even mention the duplicate functionality, that the Files app provides.
Also there isn't yet a lot of material on this topic.
So the question boils down to: Does anybody know of a way to disable this duplicate option?
Thanks in advance!
ios swift fileprovider-extension
asked Nov 21 at 13:04
SNudel
13
add a comment |
up vote
0
down vote
favorite
As the title says, I'm writing a Files app extension. In this extension the users access to some nodes will be restricted. So for example the user may only have read and create permissions on a node, meaning he can't delete anything inside that node. Therefore the move and delete options should be grayed out.
To implement this i dynamically define NSFileProviderItemCapabilities for every NSFileProviderItem based on the underlying permissions concept.
This worked for every option except the duplicate option, which seems to be enabled no matter what capabilities i assign/ not assign.
Since the user does not have create permissions on the node, the user naturally cannot create a duplicate in this location. The closest NSFileProviderItemCapabilities I found was .allowsAddingSubItems .
Example: We are in the node named "read" (the user has only read permissions for this room) therefore the NSFileProviderItemCapabilities of this room is only .allowsContentEnumerating . "read" contains a Folder "Random" which also only has the .allowsContentEnumerating capability. Since the .allowsDeleting capability is not set the delete option is grayed out and likewise since the .allowsReparenting capability is not set the move option is grayed out.
.
However the .allowsAddingSubItems capability is not set and still the duplicate option is enabled.
The apple documentation really doesn't help a lot here: https://developer.apple.com/documentation/fileprovider/nsfileproviderextension/providing_support_for_user-driven_actions doesn't even mention the duplicate functionality, that the Files app provides.
Also there isn't yet a lot of material on this topic.
So the question boils down to: Does anybody know of a way to disable this duplicate option?
Thanks in advance!
ios swift fileprovider-extension
asked Nov 21 at 13:04
SNudel
13
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
As the title says, I'm writing a Files app extension. In this extension the users access to some nodes will be restricted. So for example the user may only have read and create permissions on a node, meaning he can't delete anything inside that node. Therefore the move and delete options should be grayed out.
To implement this i dynamically define NSFileProviderItemCapabilities for every NSFileProviderItem based on the underlying permissions concept.
This worked for every option except the duplicate option, which seems to be enabled no matter what capabilities i assign/ not assign.
Since the user does not have create permissions on the node, the user naturally cannot create a duplicate in this location. The closest NSFileProviderItemCapabilities I found was .allowsAddingSubItems .
Example: We are in the node named "read" (the user has only read permissions for this room) therefore the NSFileProviderItemCapabilities of this room is only .allowsContentEnumerating . "read" contains a Folder "Random" which also only has the .allowsContentEnumerating capability. Since the .allowsDeleting capability is not set the delete option is grayed out and likewise since the .allowsReparenting capability is not set the move option is grayed out.
.
However the .allowsAddingSubItems capability is not set and still the duplicate option is enabled.
The apple documentation really doesn't help a lot here: https://developer.apple.com/documentation/fileprovider/nsfileproviderextension/providing_support_for_user-driven_actions doesn't even mention the duplicate functionality, that the Files app provides.
Also there isn't yet a lot of material on this topic.
So the question boils down to: Does anybody know of a way to disable this duplicate option?
Thanks in advance!
ios swift fileprovider-extension
asked Nov 21 at 13:04
SNudel
13
As the title says, I'm writing a Files app extension. In this extension the users access to some nodes will be restricted. So for example the user may only have read and create permissions on a node, meaning he can't delete anything inside that node. Therefore the move and delete options should be grayed out.
To implement this i dynamically define NSFileProviderItemCapabilities for every NSFileProviderItem based on the underlying permissions concept.
This worked for every option except the duplicate option, which seems to be enabled no matter what capabilities i assign/ not assign.
Since the user does not have create permissions on the node, the user naturally cannot create a duplicate in this location. The closest NSFileProviderItemCapabilities I found was .allowsAddingSubItems .
Example: We are in the node named "read" (the user has only read permissions for this room) therefore the NSFileProviderItemCapabilities of this room is only .allowsContentEnumerating . "read" contains a Folder "Random" which also only has the .allowsContentEnumerating capability. Since the .allowsDeleting capability is not set the delete option is grayed out and likewise since the .allowsReparenting capability is not set the move option is grayed out.
.
However the .allowsAddingSubItems capability is not set and still the duplicate option is enabled.
The apple documentation really doesn't help a lot here: https://developer.apple.com/documentation/fileprovider/nsfileproviderextension/providing_support_for_user-driven_actions doesn't even mention the duplicate functionality, that the Files app provides.
Also there isn't yet a lot of material on this topic.
So the question boils down to: Does anybody know of a way to disable this duplicate option?
Thanks in advance!
ios swift fileprovider-extension
ios swift fileprovider-extension
asked Nov 21 at 13:04
SNudel
13
asked Nov 21 at 13:04
SNudel
13
edited Nov 21 at 15:06
asked Nov 21 at 13:04
SNudel
13
asked Nov 21 at 13:04
SNudel
13
asked Nov 21 at 13:04
SNudel
13
13
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53412689%2fdisable-duplicate-option-in-fileprovider-extension%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
