Fix: Resolving file provider services based on security-scoped URL access#9159
Merged
Conversation
Collaborator
Author
|
/backport to stable-4.0 |
82b73f3 to
88d4c8b
Compare
…cess. Signed-off-by: Iva Horn <iva.horn@nextcloud.com>
88d4c8b to
1e62d2d
Compare
Contributor
|
Artifact containing the AppImage: nextcloud-appimage-pr-9159.zip Digest: To test this change/fix you can download the above artifact file, unzip it, and run it. Please make sure to quit your existing Nextcloud app and backup your data. |
nilsding
approved these changes
Dec 2, 2025
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.




Problem
Opening share permissions on a file provider item always failed now. There always comes up an error stating the user does not have sufficient permissions.
Underneath, the file provider UI extension fails to fetch the XPC service based on the selected file provider item.
Solution
I have written a blog post about the problem almost 2 years ago:
https://i2h3.de/filemanager-throws-error-on-getting-file-provider-services/
I do not know why it became a problem now. Maybe due to latest security updates by Apple which changed the underlying system for non-sandboxed apps.