Skip to content

fix(file-provider): reuse stored macOS domain identifier - #10748

Closed
guillebot wants to merge 1 commit into
nextcloud:masterfrom
guillebot:fix/macos-reuse-file-provider-domain-identifier
Closed

fix(file-provider): reuse stored macOS domain identifier#10748
guillebot wants to merge 1 commit into
nextcloud:masterfrom
guillebot:fix/macos-reuse-file-provider-domain-identifier

Conversation

@guillebot

Copy link
Copy Markdown

...

Minting a new UUID when getDomains fails or the stored domain is
temporarily missing creates a second Finder location. Re-add with the
same identifier, and abort instead of minting if listing fails.

Assisted-by: Cursor:grok-4.6
Co-authored-by: Cursor <cursoragent@cursor.com>
@claucambra

Copy link
Copy Markdown
Collaborator

@guillebot You have not followed the submission guidelines. Please update the PR to provide a proper description

@claucambra claucambra closed this Sep 4, 2026
@i2h3

i2h3 commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

Also, this would reintroduce one of the single most severe mistakes in managing file providers: reusing identifiers for domains. 鈽狅笍 Reusing identifiers means also reusing possibly messed up state on the file provider framework side. 馃槵 This was an intentional change I introduced in summer 2025 and must not be reverted. Also based on experience at previous companies with other file provider projects. UUID as lifetime identifiers for domains are the way to go.

@guillebot

Copy link
Copy Markdown
Author

Thank you all for the feedback. Will take it to improve my next MR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants