Uninstall claims there is no extension when its bundle directory cannot be read
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 70/100
Research direction
Read Sources/GUI/App/SystemExtensionManager.swift around lines 75-78 and 111-118, then trace how Sources/GUI/Views/UninstallView.swift presents the result. Check the signed-build behavior with a registered extension and a directory listing error. Done means the UI reports an unknown status instead of claiming no extension is registered.
Written by the indexing model from the issue text.
Description
SystemExtensionManager.swift:75-78 converts a directory-listing error into false with else { return false }. deactivateForUninstall at lines 111-118 then sets .notInstalled and skips the explicit deactivation request without checking OS registration. UninstallView.swift:290-302 says no extension was registered and there is nothing to deactivate. Finder recycling still provides a later macOS removal path at PrivilegedUninstall.swift:66-72, so this proves a false initial assurance rather than a stranded extension.
Steps
- Use a controlled installation with a registered extension and an access or I/O error listing the app SystemExtensions directory.
- Start uninstall.
- The bundle inspection returns false without an OS registration query.
- The sheet says no extension was registered and nothing needs deactivation, although registration was never checked.
Where
Sources/GUI/App/SystemExtensionManager.swift:75-78Sources/GUI/App/SystemExtensionManager.swift:111-118Sources/GUI/Views/UninstallView.swift:287-309Sources/GUI/App/PrivilegedUninstall.swift:66-72
Done when: An extension-directory read failure is shown as unknown status rather than proof that no extension is registered.
Related: #256, #214, #273
I found this reading the code and haven't reproduced it on a signed build yet: the bundle-directory read failure with an installed extension needs a signed-build check.
- Dominant language
- Swift
- Stars
- 49
- Forks
- 5
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 82
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from isaaclins/freesnitch
-
area:cli documentation good first issue priority:low
Difficulty 1/5 Under an hour Newbie friendliness 94/100
isaaclins/freesnitch#430 ·
Maintainers usually reply within 1 day
-
area:gui bug priority:low status:queued
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
isaaclins/freesnitch#428 ·
Maintainers usually reply within 1 day
-
area:shared bug priority:high status:queued type:correctness
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
isaaclins/freesnitch#284 ·
Maintainers usually reply within 1 day
-
area:helper bug priority:medium status:queued type:diagnostics
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
isaaclins/freesnitch#282 ·
Maintainers usually reply within 1 day
-
area:gui bug priority:low status:queued type:correctness
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
isaaclins/freesnitch#281 ·
Maintainers usually reply within 1 day
All issues in isaaclins/freesnitch
Similar issues
-
documentation ui
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aydenjahola/Hush#41 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
good first issue help wanted testing
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MasterJ93/ATProtoKit#354 ·
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
heysidhant/appvanish#4 ·