Uninstall 115 浏览器 on Mac

Export bookmarks and inspect downloaded files before uninstalling 115 浏览器. The browser profile is user data even when the app icon is gone. The September 20, 2026 record covers the app copied from the official package.

Quit and remove the app

Quit all 115 浏览器 windows and background processes, then move 115Browser.app to Trash. If a process refuses to quit, stop there and retry after it exits; do not force-delete a live browser profile. The official page has more product information.

Review the app’s data

The cask lists ~/Library/Application Support/115Browser, two cache roots and exact org.115Browser.115Browser preferences. The support folder is the browser profile; cache and preferences are separate rows.

If you installed it with Homebrew

The Homebrew cask has its own --zap list. brew uninstall --cask 115browser removes the cask without that list; brew uninstall --cask --zap 115browser also acts on its listed data without consulting Mole’s checkboxes. Zap includes the whole profile as well as caches. Mole skips Homebrew zap for browser casks and uses its own selected-remnant path.

brew uninstall --cask 115browser

Check the result

These commands inspect the running process and one relevant location. They do not remove anything:

pgrep -il "115Browser"
ls -ld "$HOME/Library/Application Support/115Browser"

No pgrep match means no process with that name is running; a match needs identification before quitting anything. A listed path still exists, while an ls “No such file” error means only that exact path is absent. A permission error is inconclusive.

What Mole lists

Mole leaves the 115Browser profile unselected and selects verified cache and exact preference rows by default. Mole skips Homebrew zap for browser casks so it cannot bypass those choices.

What this test covered

The September 20, 2026 official-package test initially stopped when the browser would not quit; after exit, uninstall continued. The profile remained protected and Caches/115Browser was selected. Signed-in sync was not tested.