Man… There’s nothing worse than an ugly bug rearing its head in your software. Here’s the down-low regarding the keychain issue…

As best as I can tell, if an entry was made, and then removed for some reason, it would confuse the application that was recently bundled in version 2.0.1 for the purpose of retrieving keychain entries quicker than the standard “Keychain Scripting” application in AppleScript. I’d made the change due to the fact that Keychain Scripting is a piece of unusable code that chokes on itself when dealing with more than just a few keychain entries. I could go into a long diatribe about it, but won’t. I just wish Apple would do something about it…

So, to completely resolve all keychain problems, I’ve removed every single line of keychain related code from Yasu. For those who were overjoyed that it was added, I’m sorry to have to take the candy away from you. But fear not. I will be working on a proper implementation of keychain storage in a future version.

To be completely honest though, I feel really good about removing the option. It was the one area of the application that I never felt very comfortable with, and always thought it had the potential for the unreliability it proved itself to have. Now that it’s gone, Yasu is much faster at authenticating, due to the fact it doesn’t have to search through every keychain key before putting up the authentication dialog.

The moral of the story? Go with your gut. That, and test the heck out of your application, then test the heck out of it again, and finally test it a few more times before testing it again a few more times…

It would appear there may be some keychain issues going on with Yasu. I’ve not been able to track them down or reproduce them myself, but if Yasu is to blame, that’s just plain bad.

To alleviate the problem, I plan to update Yasu this evening to remove all keychain interaction, thus solving the problem entirely. For those of you that were so happy about having the ability to save to the keychain – so sorry to take it away, but it’s not worth the trouble it seems to be causing.

Keep an eye out for an update soon. For those who this may have been affected, my sincere apologies.

[UPDATE] – I have been able to reproduce the issue on my own machine (Don Fraser – sorry for not believing you sooner), and I know what the problem is. A fix will be out shortly…