-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Selfcontrol-cli can't read blocklist from default directory #853
Comments
If you save the blocklist in the app is the resulting file identical to the |
A bit of research on this: it appears that the file stored at Copy of the blocklist from
Exported file containing the same blocklist:
It appears they contain very similar information, but are definitely not the same. |
After doing a search for files with the same MD5 hash as the exported blocklist, it appears none exist in either ~/Applications or ~/Library/Preferences, which leads me to believe that the blocklist recognized by the SelfControl frontend application and the CLI are using two different formats for blocklists. Pure speculation, but I'd imagine the copy in Being able to access the blocklist defined by the user in the GUI would be enormously helpful - I am currently building out a SelfControl Raycast extension for my own (and others) use, and being able to use the GUI-defined blocklist rather than having to re-export changes to a specific file location in the user's home directory would be awesome. |
Summary
Selfcontrol-cli does not seem to be able to read the blocklist in the default directory. This command results in an error:
Background Info
SelfControl version? 4.0.2
macOS version? 13.5
Do you use a VPN/proxy, and if so which one? No
Has this ever worked for you on a prior version of SelfControl? If so, when?
Any other special system setup we should know about?
How Do We Reproduce This Issue?
Describe detailed steps that reliably make this issue show up. For example, "start a block containing 5 websites, click button X, then button Y"
Run the command as listed above.
What Should Have Happened?
I expected the selfcontrol block to start.
What Actually Happened Instead?
Selfcontrol-cli could not read the blocklist from the default directory.
The text was updated successfully, but these errors were encountered: