Good news! I updated my Retina MacBook Pro to 10.12 Sierra and TotalFinder seems to be working well. I have been using Visor and Dual Mode frequently, so far with no real issues. Finder itself now has a Folders On Top feature but there seem to be no ill effects when used with TotalFinder. The additional context menus seem to work fine too.
Of course I do have system app protection disabled with SIP, but I didn’t have to do anything special after updating my El Capital system with TotalFinder already installed.
Overall I’m quite pleased that updating caused no problems whatsoever for me. I hope everyone else has a similar experience!
Just wanted to chime in to say that I’m getting the same frequent crashes with the same exception/description as @Guid0man.
The crash seems to occur when I:
(1) Click on the sidebar in TF when I am more than one folder deep in Column View; in other words, if I am at the highest folder level (e.g., the first column), then I click on the sidebar, no crash occurs. However, if the focus is currently on the second column or later, then I click on the sidebar, TF goes crashy-crash.
(2) Right-click to “show package contents” on some types of packages. For example, I can “show contents” on a .app file, but not a .osax or .bundle file. Specifically, I use a custom re-colored Visor button (sorry, not a fan of the default purple-y color ) and TF crashes consistently when I attempt to “show contents” on TotalFinder.osax.
Currently running Sierra build 16A238m. I will re-post if I find any more specific crash triggers.
Just updated to Sierra build 16A254g and it appears the crashes have stopped for me; the crash triggers I described above are no longer causing problems. Will update if problems return.
Is there any different method to disable SIP on Sierra that is required? I’ve tried running through the instructions provided for El Capitan (and that have worked for me on that release) to no avail with the Sierra betas. I still get the Totalfinder crash immediately upon startup.
Here are the results. I also emailed the crash log using the built in error reporting dialog.
Aug 24 07:55:58 Jays-iMac TotalFinderCrashWatcher[1679]: ‘/Users/plater/Library/Logs/DiagnosticReports/Finder_2016-08-24-075557_Jays-iMac.crash’ crash report was related to the target app -> open Crash Reporting Dialog
Aug 24 07:56:20 Jays-iMac TextExpander[1658]: Secure event input has been enabled by: TotalFinderCrashWatcher (com.binaryage.totalfinder.crashwatcher)
Aug 24 07:57:07 Jays-iMac spindump[1110]: Saved spin report for TotalFinderCrashWatcher version 1.6.27 (1.6.27) to /Library/Logs/DiagnosticReports/TotalFinderCrashWatcher_2016-08-24-075707_Jays-iMac.spin
Aug 24 08:15:29 Jays-iMac TotalFinder[959]: agent v1.6.27 started (TotalFinder)
Aug 24 08:15:31 Jays-iMac TotalFinder[959]: requesting injection into com.apple.finder[843]
Aug 24 08:15:31 Jays-iMac Finder[843]: TotalFinderInjector v1.6.27 received init event
Aug 24 08:15:31 Jays-iMac Finder[843]: TotalFinderInjector: You have Finder version 10.12. But TotalFinder was properly tested only with Finder versions in range 10.8.0 - 10.10.5.
Aug 24 08:15:31 Jays-iMac Finder[843]: TotalFinderInjector: Installing TotalFinder from /Library/ScriptingAdditions/TotalFinder.osax/Contents/Resources/TotalFinder.bundle
Aug 24 08:15:31 Jays-iMac Finder[843]: Warning: Finder has unknown version 10.12. TotalFinder has not been tested with this Finder version.
Aug 24 08:15:31 Jays-iMac Finder[843]: TotalFinder was unable to resolve 1 Finder classes. Please update TotalFinder.
Aug 24 08:15:31 Jays-iMac Finder[843]: Launching TotalFinderCrashWatcher from '/Library/ScriptingAdditions/TotalFinder.osax/Contents/Resources/TotalFinder.bundle/Contents/Resources/TotalFinderCrashWatcher.app’
Aug 24 08:15:31 Jays-iMac TotalFinderCrashWatcher[1093]: Watching ‘/Users/plater/Library/Logs/DiagnosticReports’ for new crash reports with prefix 'Finder’
Aug 24 08:16:02 Jays-iMac TotalFinder[959]: TotalFinder has been succesfully injected into com.apple.finder[843
<< I updated my Retina MacBook Pro to 10.12 Sierra and TotalFinder seems to be working well. . . . I didn’t have to do anything special after updating my El Capitan system with TotalFinder already installed. >>
I too had no problem with TotalFinder (v 1.8.0) after updating to Sierra on my rMBP. On my retina iMac, however, TotalFinder will not launch after updating to Sierra. I keep getting the error message: “Troubles launching TotalFinder. Apple Events cannot be delivered.” I repeatedly tried the recommended maneuver in the Terminal (sudo killall -KILL appleeventsd), but that hasn’t remedied the problem. I’m open to other suggestions!
Sorry for the radio silence. Please confirm your Sierra build version so I can take a look. Apple seems to be seeding slightly different builds to different beta testers.
Some days ago, I encountered a problem with 1.8.1 that I can’t recall now. It might have been some non-responsiveness. I also noticed in the update dialogue box that 1.8.1 had been “removed” for some other reason. That prompted me to go back to 1.8.0, which has given me no problems to speak of.
I always got this internal error when I was double tapping or right clicking.
Exception Name: NSInvalidArgumentException
Description: +[NSArray FINodesFromFENodeVector:]: unrecognized selector sent to class 0x7fffcca8ea80
User Info: (null)
