I have Codebook 4.3.3 on my macOS Catalina 10.15.7. With one of the recent updates to Codebook in the past month or so I’m noticing that Codebook will crash when it auto-locks from not being used (I have mine set to the default of after 5 minutes). Apple gives me the opportunity to send the crash report to them.
Reproduction Steps:
Ensure Codebook is not running
Use Secret Agent key command to launch Codebook
NOTE: I could not reproduce this by manually opening Codebook and then using Secret Agent; it only reproduced when using Secret Agent to launch Codebook if it’s not already running.
Select a password (or other field) for Codebook to auto-type into someplace.
Wait for timeout (5 min default).
Codebook will crash instead of lock.
I have the crash report available. How should I submit it for review?
Thanks very much for using Codebook and posting to this discussion forum with the crash report and steps to reproduce it. We are aware of the issue and have a fix prepared that we’re testing internally. We should be releasing a beta version of Codebook shortly which includes a fix for this issue. I’ll post back to this thread when the beta build is ready to have you try it out and confirm it’s resolved on your end.
In the mean time to workaround this issue you can either:
Launch the main Codebook app and login prior to triggering Secret Agent
Set the AutoLock timer for a longer period of time
I’ve just published the beta build which includes a fix for this issue. Here are the steps to access it if you’re using a Codebook build distributed by Zetetic (as opposed to through the Mac App Store):
Launch Codebook and login.
Navigate to Codebook menu > Preferences > Updates Tab
Set the Release Channel to beta and click the Check For Updates button.
A new update window should appear for the 4.3.4 (882) build, click the Download button to download the package installer and then run it to install.
Excellent. Glad the beta resolved the issue for you as well.
Thanks again for taking the time to write up the report and please feel free to reach out again if you have any further questions, issues, or feedback.