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.
She deleted the lockfile. Then she went to ~/Library/Saved Application State/ and deleted com.clio.desktop.savedState . Corrupted state data from a crash two weeks ago had been poisoning every launch attempt. clio desktop app not opening
The next morning, she wrote to Clio support with steps to reproduce: “Lockfile persistence + corrupted saved state = silent failure on launch.” They thanked her. A junior engineer later confirmed it was a race condition in the Electron shell’s ready-to-show event, triggered only when a previous crash left a zombie lockfile. Instead of brute force, she switched to forensic calm
The login window appeared. Clean. Responsive. She logged in. Her offline entries were still there, preserved in the local database now freed from the lock. She synced. She generated the invoice. She attached the PDF. She emailed the client at 11:43 PM. She saw a file: Lockfile