Deeper help
troubleshooting

Troubleshooting

Common issues and how to fix them. If none of these help, send a bug report — it's the fastest way to get it looked at.

The app won't open

Deeper is signed and notarized by Apple, so a normal install shouldn't trigger a security warning. If macOS still refuses to open it:

The server shows a port conflict

Deeper's built-in server uses port 52713. If another program (often a leftover copy of Deeper) is already using it, settingsSERVER shows a port-conflict message with a kill conflicting process and retry button. Click it to reclaim the port.

The phone won't connect

Most connection problems come down to the network. Work through these:

A track shows but won't play

On the Mac: if a track is in your library but won't play, its audio file has usually been moved, renamed, or deleted outside Deeper. Use right-click → show in Finder to check whether the file is still there; if it moved, re-import the folder it now lives in.

On the phone: a track only plays offline if it's been downloaded. If you're away from your Mac and a track is greyed out or shows "not downloaded", it wasn't part of a synced-and-downloaded playlist. Sync and download it while connected. See iPhone companion.

No sound during playback

If the player's output device name is highlighted in amber, audio is being routed to a virtual or loopback device (like BlackHole) and won't be audible. Switch your Mac's sound output back to your speakers or headphones.

Reporting a bug

The in-app reporter is the best way to flag a problem. In the Mac app, choose HelpReport a Bug... (also available from settings), describe what happened, and send. Reports include app logs to help diagnose the issue — those logs can contain track names and file paths. If the app ever crashes, a crash report is sent automatically so it can be fixed.