Uninstall claims there is no extension when its bundle directory cannot be read

Open
#288 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
70/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
macos, swift
Domain
desktop, security

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

area:gui bug priority:low status:queued type:diagnostics

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

  1. Use a controlled installation with a registered extension and an access or I/O error listing the app SystemExtensions directory.
  2. Start uninstall.
  3. The bundle inspection returns false without an OS registration query.
  4. The sheet says no extension was registered and nothing needs deactivation, although registration was never checked.

Where

  • Sources/GUI/App/SystemExtensionManager.swift:75-78
  • Sources/GUI/App/SystemExtensionManager.swift:111-118
  • Sources/GUI/Views/UninstallView.swift:287-309
  • Sources/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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from isaaclins/freesnitch

All issues in isaaclins/freesnitch

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.