Skip to main content

❓ FAQ & Troubleshooting

Common questions and resolution steps for issues encountered while using leetrs.

🔒 Authentication Issues​

Symptoms: Error message Failed to extract cookies from <browser>.

Solutions:

  1. Open your browser and verify that you are logged into leetcode.com.
  2. Run with verbose diagnostic logging: leetrs --verbose auth (or leetrs -v auth) to see exactly which database paths, profile directories, and keyring candidates were scanned by the cookie-extract engine.
  3. Database File Locking: Unlike older tools that locked when browsers were running, cookie-extract safely stages temporary copies of the SQLite databases and transaction logs (-wal / -shm), so you do not need to quit your browser.
  4. Windows Chrome 127+ App-Bound Encryption: Recent Windows Chrome updates restrict out-of-process DPAPI decryption. If cookie-extract reports AppBoundRestricted, select "Paste cURL / Cookie header manually": in your browser's Developer Tools (F12 → Network tab), right click any request → Copy as cURL, and paste directly into leetrs auth.
  5. If using a remote SSH session or unsupported browser, choose "Paste cURL / Cookie header manually" to paste tokens directly.

⚡ Neovim & Editor Issues​

Neovim fails to launch after leetrs pick​

Symptoms: Error failed to launch nvim. is it installed and in your path?

Solutions:

  1. Check if nvim is installed and in your $PATH: 
    which nvim
  2. If using another editor (e.g. VS Code), set editor = "code" inside ~/.config/leetrs/config.toml.

💾 Cache & Data Issues​

How do I refresh problem cache?​

Solutions: If problem metadata or solved statuses appear outdated:

# Delete local data cache
rm -rf ~/.local/share/leetrs/data.json

# Re-run TUI to trigger sync
leetrs tui