Homebrew: Error: It seems there is already an App at '/Applications/Chrome.app'
A cask install failed because the app is already installed manually (or a leftover exists).
Error: It seems there is already an App atIt seems there is already an App at '/Applications/Error: It seems there is already an App at '/Applications/Docker.app'cask already an app at Meaning
Adopt the existing app into Homebrew with brew install --cask --adopt NAME, or remove the old app, or use --force to overwrite. Don't mix manual and cask installs of the same app without adopting.
Common causes
- App installed outside Homebrew
- Leftover app bundle after a failed uninstall
- Different app with the same name
- Quarantine/permissions blocking removal
- Cask renamed
⚡ Quick fix
brew install --cask --adopt NAME- Remove the old app and reinstall
brew install --cask --force NAME
Detailed fix by platform
macOS
brew list --cask | grep -i NAME && ls -ld /Applications/NAME.app
How to diagnose
- Installed — Manually or via cask?
- Option — Adopt or force?
- Leftover — Old bundle?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- "x" can't be opened because it is from an unidentified developer macOS: “app” can’t be opened because it is from an unidentified developer
- Apple could not verify "x" is free of malware macOS: “app” cannot be opened because Apple cannot check it for malicious software / Apple could not verify “app” is free of malware that may harm your Mac
- Bad configuration option: usekeychain ssh: /Users/me/.ssh/config: line 5: Bad configuration option: usekeychain
Most viewed in macOS
- is damaged and can’t be opened macOS: “App” is damaged and can’t be opened. You should move it to the Trash.
- Operation not permitted (macOS privacy) macOS: Operation not permitted — Terminal/app lacks Full Disk Access (TCC privacy protection)
- Docker Desktop requires privileged access (vmnetd) macOS: Docker Desktop needs privileged access / com.docker.vmnetd could not be started
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026