Handle dangling Xcode selection symlinks - #6
Merged
Merged
Conversation
MattKiazyk
approved these changes
Sep 8, 2026
Contributor
|
Thanks! |
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
2 participants
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
Creating a new selection link fails when
/Applications/Xcode.appis a dangling symlink.FileManager.fileExists(atPath:)follows symlinks and returnsfalsewhen the destination is missing. As a result, the existing symlink is not removed, and creating its replacement fails because an item namedXcode.appstill exists.Changes
Use
attributesOfItem(atPath:)to inspect the filesystem entry itself, allowing dangling symlinks to be identified and replaced.Real Xcode app bundles remain protected from being overwritten.