I have the same problem!
Very strange… I have also just experienced this. I just upgraded to TF 1.6.6 and all was working just fine until I logged out then back in again. Now I see the same error messages when running from Terminal.
I am running Yosemite beta, however, not 10.9.4
Same problem here…after installing 1.6.6. this morning
I did some changes in the launching agent. Have to review them again. Several people reported this already.
Ok, guys. I have found the problem. It was introduced in 1.6.6. It will be fixed in 1.6.7.
Historically TotalFinder (and TotalTerminal) do not hook into Finder binary immediately after injection request. They give binary some time (typically 2 seconds) because of some edge-case situations for example when binary has been just lunched during startup and is busy doing window restoration or similar init operation it is not good to mess around with TotalFinder swizzling at this point.
This has been working pretty well, but there were two issues:
- some applescript utilities expect TotalFinder to be ready after issuing injection event (not eventually after few seconds)
- the delay was effective every time, even for injection into already running binary
In 1.6.6 I decided to make injection event instant and implement this delay logic in TotalFinder.app (agent) which is responsible for sending injection events when you launch it (or relaunch it). And also to make it smarter: agent should check how old the app is and apply delay only if the app was just launched few moments ago. This would solve both #1 and #2.
This should be working fine. But for delay I did one technical mistake. I was caching NSRunningApplication instance to reuse it later. This is not working properly. When timer fired, the instance was already in some bad state and reported that process has been terminated (but it was not).
The solution is not to cache NSRunningApplication instances, but cache plain old process identifiers and lookup NSRunningApplication instance dynamically.
Same symptom and same console message. This is 10.9.4.
Workaround should be just launch Finder.app (via Dock icon for example) and then wait and launch TotalFinder.app after few seconds.
The workaround did not work for me.
Unfortunately no success here, too.
Ah, too bad
I have just tested it on clean machine and working workaround is to execute this line in Terminal.app:
osascript -e "tell application \"Finder\" to «event BATFinit»"
I’m going to release a new version today. Unfortunately most beta users affected by this had to downgrade or their TotalFinder is not running anymore.
I wonder how is this possible, because standard codepath should be exactly the same as in old versions.
I can’t answer your rhetorical question, but can tell you the glitch reminded me how much I value TF.
agree!! I love TF !haha I’m waiting for the new released
I’m about to put 1.6.7 to beta channel:
I tested it myself under clean 10.8, 10.9 and 10.10 systems. But I would be glad if you guys could test it too. TotalFinder should launch after installation and after next system reboot.
My conclusion is that the bug was there all the time, but it got exposed when I changed the code. For example 1.6.6 works fine under 10.8. It simply does not expose same behaviour as under 10.9 and 10.10.
So far, so good here. Everything seems to be working normally, even after a reboot. Thanks for the quick fix!
TF-1.6.7 again working as usual, that means simply great, on my Mountain Lion, Mavericks and Yosemite Beta installations.
Thanks, Antonin, for your restless work and quick response.
1.6.7 Working. Thank you!
TF 1.67 loads, but the minimize button (yellow) in the upper left hand corner does not work for me.
I have the same problem: 1.67 is fine, except the minimize button