-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Corrupted preferences file stops the app from being able to run #62
Comments
Unfortunately, I can't reproduce this error on my machine to debug it. I'm running Ventura 13.3.1, tried my existing install and its working okay. I've also just downloaded a fresh version of 1.5.0 and cleared out all preferences and permissions, its also working okay via the right click open method at first, then just double click from then on. I can't really do anything more as I can't get it not to work. :/ |
odd, ok, thanks for looking! Still not sure what's up with mine. I open in with the right click, but it just immediately closes. I even tried opening it from the command line to see if there was an exit code or something, but didn't much of anything, just this:
|
I think I had a bad plist file. After deleting it and running For reference, this is what my file looked like before:
This is after:
|
Interesting... thank you for debugging and sharing a working solution. I'm not 100% sure what the issue is based on that snipped due to the encoding, but at a guess the app didn't cleanly write the preferences file. I should perhaps add in a provision for the preferences file being corrupted during app boot. I'll re-open this issue and re-title it, although not sure when I'll get around to adding that provision in. Thanks again! |
Description
Even when trying to right click and open thing, it will no longer open on the latest macos
Version
1.5.0
Steps to Reproduce
Download app
Put in applications folder
attempt to open with right click -> open
Screenshots
No response
Device
MacBook Pro
Operating System
macOS 13.3.1
Additional Context
No response
The text was updated successfully, but these errors were encountered: