Executive Summary

SuperDuper! 4.0.1 now available in-app, and as a direct download.

Never have I ever

Never have I ever released a major version without following it up with a “quick fix” release. The saying is true: no plan survives an encounter with the public.

Or, as Mike Tyson said, everyone has a plan ‘til they get punched in the mouth.

So, thanks for punching me, oh-so-lightly, in the mouth. More like a love tap. Because things are working better than I’d hoped, given the sheer amount and complexity of the new code (namely, all of it).

Also, and I don’t say this enough, thank you to everyone who reached out to send a kind word. Developing something like this in relative secrecy can be lonely, as you wonder whether changes this extensive are going to hit folks as a good thing, Release day itself is full of detail work, and I was doing a lot more than just posting a build: a whole new website, self-implemented blog engine, dynamic page release notes…it was quite a lot!

But now that it’s all finally out in the wild, the positive feedback has been encouraging, and I really appreciate the time each of you spent to send it in. Thanks.

The windup, and the pitch

So, you might ask, with all that said, what’s wrong, then? Well:

• There was a timing related issue with Backup on connect that caused a backup to fail, before it started, if the APFS container mounted quickly, but its volumes mounted slowly.
• In some situations, Backup on connect would only work once until the server was restarted.
• An encrypted drive would fail to unlock if there were bad credentials in the keychain along with good ones.
• I missed a few time localizations (embarrassing; sorry, non-US folks).

And that’s it. So far. Let’s hope it stays that way!

The new update is available in-app, of course, or you can download and install manually.