How to uninstall approf on Mac

Save pprof profiles and any wanted sessions before quitting approf. This guide covers the downloaded Mac app, with Homebrew handled separately below.

Quit and remove the app

Keep Graphviz and original profiles when other tools still use them. A small configuration file of unknown scope was retained in the test.

Quit approf using its own quit action. In System Settings › General › Login Items & Extensions, turn off any approf login entry if present. After backing up, move /Applications/approf.app to Trash in Finder and leave Trash intact until the wanted data is confirmed saved.

Project documentation.

Review local data

Use Shift + Command + G in Finder to inspect each complete path. Copy wanted contents elsewhere before deciding to move that item to Trash. These locations come from the recorded test and the live Homebrew cask. Do not create a missing path. A * marks a matching range, not a literal filename; inspect the actual matches individually.

If you installed it with Homebrew

To uninstall without running zap:

brew uninstall --cask approf

This removes the cask-managed app; the cask also requests that its matching app quit, without running its zap data list.

The following direct command applies the cask’s entire zap list independently of Mole’s checkboxes. Use it only after backing up and approving every target.

brew uninstall --cask --zap approf

The live zap targets are ~/Library/Application Support/the.future.app.approf.approf.plist, ~/Library/Caches/the.future.app.approf.approf, ~/Library/Cookies/the.future.app.approf.approf.binarycookies, ~/Library/HTTPStorages/the.future.app.approf.approf, ~/Library/LaunchAgents/the.future.app.approf.approf.plist, ~/Library/Preferences/the.future.app.approf.approf.plist.

Group folders, containers and support folders may contain wanted data. Use the command without zap when retaining any of them. Live cask.

Check the result

ls -ld '/Applications/approf.app'
pgrep -ifl '/Applications/approf[.]app/'

A listed app path means that bundle remains. “No such file or directory” means that exact path is absent; “Permission denied” leaves the check unconfirmed. This checks one location, not other copies, background services or user data.

A pgrep result means a running command line matches this app path. No output means no such match, not that independent helpers or other app copies are absent; an error leaves this step unconfirmed.

What Mole lists

• ~/Library/Preferences/the.future.app.approf.approf.plist is selected by default.

These defaults assume “Remove data and settings with apps” is off, which is the default. Enabling it also selects eligible reviewed app data; shared and protected items retain their individual boundaries. Mole invokes Homebrew zap only when the whole zap scope passes its check. Unchecked, shared or out-of-boundary paths and unsupported directives suppress zap; selected remnants still use Mole’s own deletion flow.

What this test covered

Removal used a source-built Mole app. The recorded first-launch scan was partial and does not establish every file the app can create.

First launch stopped at the missing-Graphviz screen. The official app and reviewed paths were removed; an additional configuration file was retained. Profile rendering, saved sessions and the update page were not tested.