Docs / Troubleshooting
The Library could not be read
JSpark never deletes a Library it cannot read. The message says where the file is.
What happened
JSpark keeps your Saved Snippets in one file, library.db. When it opens and cannot read that file, it shows one of two messages. The reason is at the end of each, in brackets.
| The message | What it means |
|---|---|
| Your Library couldn’t be read | The file is damaged. JSpark moved it aside, to a name that ends in .unreadable- and the time, and started a new, empty Library. The old file was not deleted, and the message shows where it is. |
| Your Library couldn’t be opened | The file is there but could not be opened, and it was left where it is. For now, JSpark uses a Library that is not saved: anything you save is gone when you quit. |
Your open tabs are kept in a file of their own, so they are not affected.
What to do
- Press Show in Finder (Show in Folder on Windows) to see the file.
- Keep that file. Do not delete or move it.
- If the message was couldn’t be opened, do not save to the Library yet. Quit JSpark and open it again: it tries to open the file at every launch.
- If the message comes back, or the Library was damaged, report it with Help → Report a Problem…, and include the reason from the message. See Report a problem.
Bring back an export JSpark+
If you exported your Library to a .json file before, choose File → Import Library… and pick that file. Importing only adds Saved Snippets: nothing already in the Library is replaced. Importing is JSpark+; exporting works in JSpark too. See Export and import.