Clio Desktop | App Not Opening

The app never failed again. But she never clicked that column icon without a half-second pause, a silent prayer, and a backup browser tab already open to Clio Web.

It was 9:47 PM on a Sunday. Priya had just finished a 14-page heritage report for a museum client. The deadline was midnight. All she needed to do was open Clio, log her final three hours of work, generate the invoice, and attach the PDF. clio desktop app not opening

Instead of brute force, she switched to forensic calm. She opened Terminal. Navigated to ~/Library/Application Support/Clio/ . She saw a file: Lockfile . That shouldn’t be there. A lockfile means the app thinks it’s already running—even after a reboot. The app never failed again

10:58 PM. Priya stared at the frozen icon. She imagined emailing the client at 11:30 PM: “Sorry, can’t invoice you because my time-traveling database column won’t wake up.” She felt the familiar shame of a creative pro betrayed by a tool she had trusted. She even tried opening Clio Web in Chrome. It worked—but her offline time entries (the three hours she logged while at a coffee shop with no Wi-Fi earlier that day) were not synced. They existed only inside the dead app’s local cache. Priya had just finished a 14-page heritage report

Now Clio demanded a fresh login. But she couldn’t log in, because the app wouldn’t stay open long enough to type her credentials.