November 23rd, 2015 by Jon
November 12th, 2015 by Jon
So I started getting emails yesterday complaining that Jettison was suddenly telling users their trial period was over – even though they’d already purchased a license. When I got the first few, I thought they’d just deleted their preference files and needed to re-activate their licenses, but then the trickle became a deluge – what the heck?
So I dropped everything and looked into it – I needed an answer ASAP or I was gonna spend the next couple of days doing nothing but answering email. It turns out everyone who was affected had bought Jettison through the Mac App Store and then upgraded to the direct-from-the-website version (because it’s better, of course – instructions here if you’re interested). When you do this, Jettison copies your Mac App Store receipt to a safe place so that it can verify that you’ve actually bought a license, even if you delete the App Store copy of Jettison.
Lucky for me, I’d bought a copy of Jettison myself when testing this mechanism, so I had my own receipt still sitting in ~/Library/Application Support/ so I could look at it. Printing the certificates in the receipt showed this little tidbit:
Signature Algorithm: sha1WithRSAEncryption
Issuer: C=US, O=Apple Inc., OU=Apple Worldwide Developer Relations [...]
Not Before: Nov 11 21:58:01 2010 GMT
Not After : Nov 11 21:58:01 2015 GMT
Subject: CN=Mac App Store Receipt Signing, OU=Apple Worldwide Deve [...]
See that “Not After:” entry in the Validity section? “Nov 11 21:58:01 2015 GMT” – yeah, that’d be yesterday. When the emails started. Apple signed the receipt with a certificate that expired yesterday, so if you have one of these receipts, Jettison no longer thinks you’re legit. Sorry about that – I hadn’t considered that eventuality. And reading the news this morning, it appears that Apple hadn’t either.
So what to do? I’ve wrapped up Jettison 1.5 and posted it. You’re going to have to do a little dance again to get Jettison to update your receipt, but this version will do the right thing once you follow these instructions:
- Put every copy of Jettison on your Mac in the Trash and empty the Trash.
- Open the App Store application and click on the Purchases tab.
- Re-download the copy of Jettison you purchased. It will include a new, non-expired receipt.
- Download the latest version of Jettison (http://www.stclairsoft.com/download/Jettison-1.5.dmg)
- Double-click the .dmg file to open it, then double-click on Jettison before copying it to your Applications folder.
- After Jettison tells you that it has found your App Store license, you can copy it to your Applications folder.
Sorry for the hassle. But hey, at least it forced me to get the version 1.5 update out the door, so there’s some benefit there, eh? And thanks Apple – I didn’t need to sleep last night anyway.
P.S. I’m seeing a bunch of people buying non-App Store licenses directly from the St. Clair Software store today instead of jumping through these hoops to deal with the App Store. I have to say I’m all for that
A bit more info that’s interesting and could use some corroboration: I think this problem only affects apps that were downloaded before September 24 (either via purchase or update). When I download a new copy of Jettison from the App Store, the receipt is signed with a cert valid within these dates:
Not Before: Sep 24 19:09:31 2015 GMT
Not After : Oct 23 19:09:31 2017 GMT
So in my sample size of 1, copies of Jettison purchased or updated today will work until Oct 23, 2017, and could have worked with this receipt only as far back as September 24. If Apple has been using the same certificate to sign all App Store receipts (which seems reasonable), then anything that has been downloaded from the App Store after September 24 won’t expire until 2017. And apps downloaded prior to that have some other expiration in their receipts. If I had more time, I’d dig through all of my App Store apps to find out when each cert expires, but alas, I’ve got work to do and have killed enough time on this already…
November 10th, 2015 by Jon
So there was some faulty logic in 5.0b2 that caused the shortcuts for Favorites to be pretty flaky – sorry about that. They’re fixed in b3, along with numerous other things (some of which didn’t make it into the release notes, now that I’m looking at them again). The biggest changes in b3 are internal – I spent quite a bit of time tightening up Default Folder X from top to bottom to make sure that no resources are left open, in hopes of fixing the “The application Default Folder X is not open anymore” error message that some of you have gotten. You may see that error one more time (and will have to restart to make it go away), but it shouldn’t occur when Default Folder X auto-updates in the future (from b3 to b4, for example). If it does, please let me know!
Progress has been slower than I’d like over the last few days – mostly due to the aforementioned analysis of Default Folder X’s internals – and now that’s done and the flaky shortcuts are fixed, I should be able to get back to forward progress.
As always please let me know if you encounter any issues or have any suggestions!
Oh yeah – you can get the new build with “Check for Updates” if you’ve already got b2 running on your Mac, or go to http://stclairsoft.com/DefaultFolderX/beta.html and download it from the link at the bottom of the page.
P.S. Yes, I know that the buttons at the top of the beta page download version 4. If you’re beta testing, you should certainly be patient enough to read through the page and find the link at the bottom. Let’s just call that a first-order filter to get into the beta program 😉
November 7th, 2015 by Jon
Thanks to everyone that’s given me input and bug reports on the first public beta of Default Folder X 5. There’s now a new build based on your feedback – you can can click “Check for Updates” if you’re already running 5.0b1, or grab it from:
If you submitted a bug or feature that’s not in yet, that doesn’t mean I’m not listening. I was just anxious to get this build out because it fixes several big problems that affect quite a few people.
I’m particularly happy that I was able to find the bizarre one that was causing the Save button to stop working in save dialogs. It’s actually a bug in OS X that Default Folder X was triggering – get this: If a file dialog is showing the contents of a folder and you tell it to show the contents of that same folder, the Save button stops working. Who knew? So the hugely complicated fix was just to make sure that Default Folder X checks to see what the current folder is, then just does nothing if the file dialog is already showing the folder it wants to go to (which it really should have been doing all along in the interest of efficiency anyway).
You can reproduce the bug by hand pretty simply (turn off Default Folder X before doing this – otherwise its Finder-click feature will get in the way):
- Run TextEdit
- Create a document
- Choose File -> Save
- Switch to the Finder and drag any folder into the file dialog to make the dialog show that folder
- Drag that same folder to the file dialog again
- Now try to click the Save button. It doesn’t work!
Pretty cool, eh? Not really >:( This has been stressing me out for a couple of days because I had no idea what was going on. Glad it turned out to be easy to fix after a bunch of you helped me track it down and reproduce it here. It’s really nice when beta testing works like it’s supposed to
So thanks everyone! And keep the feedback coming.
November 5th, 2015 by Jon
November 4th, 2015 by Jon
October 30th, 2015 by Jon
October 16th, 2015 by Jon
Wow – I’m getting inundated with email and tweets asking what the status is and when it’s going to be done. It’s great to hear from everyone and I’m sorry to keep you waiting. Some bits have taken quite a bit longer than I expected :-/
So, taking a break from coding for a few minutes, here’s a summary of where things are:
- File dialog stuff is all working except for handling default folders. Recents, favorites, hierarchical menus and the new drag and drop bar work well. Here’s a quick screenshot of what’s on my screen today (that’s the tagging view showing below the dialog, including recently used tags, and the drag and drop bar on the left).
- DFX now also automatically adds a button to your Finder toolbar, and clicking it slides out the drag and drop bar below the current Finder window. This lets you toss a file into the bar, switch to another Finder window, and then drag it to where you want it.
- There’s more information in the attribute tabs below the file dialogs and it all works more smoothly than it did in v4 (and the code is way better now – much easier for me to work with!).
- Update checking just went in – it wasn’t hard, but just hadn’t been on my hot list until I got all DFX’s basic features working and debugged well.
- So what’s left? The big thing is getting the preferences finished. There’s a lot of configurable stuff under the hood (the menu structure, shortcuts for a ton of things, etc), but I may hold off on actually putting that in the prefs due to the amount of time involved. Other things: I have to drop in the licensing engine and get the upgrade process put together (both for licensing and upgrading from old prefs).
- There are still a lot of features and suggestions on my To-Do list, but I’m making sure the fundamentals work well for the first release and getting it into people’s hands as quickly as possible, given how much feedback I’m getting that you just want that stuff to work on El Capitan first and foremost.
- Oh, and yes, there’s the appearance… This is what I’ve got now, and like v4, version 5.0 will probably ship with one appearance. Then you’ll all send me hate mail about what you think of the new look and I’ll add other appearance options (including something that takes up less screen real-estate).
I’m trying to balance features with getting it into your hands ASAP.
So the bottom line? We’re half way through October and it’s not feature-complete, so it’s not going to be fully tested and done by the end of the month, as much as I’d like it to be But I’ll have a public beta in your hands by the end of October that will be solid and will get your workflow sped back up again.
OK – back to work….
September 22nd, 2015 by Jon
Version 4.7.4 of Default Folder X is now available, bringing several compatibility updates such as support for the latest version of TypeIt4Me. If you’re running El Capitan, it will also detect System Integrity Protection (SIP) and let you know that Default Folder X is only compatible with El Capitan if you turn SIP off. Of course, if you’re here reading this, you already know that and don’t need the warning message, do you? In any case, details and download links are on the Default Folder X Release Page.
Speaking of El Capitan, I’ve now put together a longer explanation about what’s going on with System Integrity Protection, how to turn it off and why the current version of Default Folder X needs it turned off – you can read it here.
Happily, version 5 of Default Folder X is coming along well and we’re using development versions of it in-house. I wish I could just wave my hands and have it finished, but with something like Default Folder X there’s quite a bit of experimentation and invention involved in the development process. Some features work as expected, while others uncover bugs in OS X or quirky behavior that then requires a day or two of wrangling to get working right. It can be a frustrating process, but is exciting when things start coming together and really working well – and I’m getting to that point
Anyway, grab version 4.7.4 of Default Folder X and I’ll keep you posted on the progress of DFX 5. Oh, and just to make our policy clear, the version 5 upgrade will be free to anyone who purchases version 4 now.