would be great if you could also try with 5.663: https://folivora.ai/releases/btt5.663-2025092602.zip
Hi! I just tried it, and it hasn’t crashed so far! It’s working perfectly.
- 1st instance: I closed my working instance of BTT and replaced the previous version of BTT (5.640) with 5.663. I reopened BTT from the Applications folder and it successfully opened.
- 2nd instance: I restarted my Macbook to test it again, and BTT opened successfully as part of the Login Items. I manually quit it, and tried opening it via Spotlight; it successfully opened again. I manually quit it again and tried opening it via Alfred, and it successfully opened once again!
No additional crash logs have been present in the Console app. Thank you!
5.663 is working for me too!
That’s awesome! This was a hard one to figure out
thanks for all the testing!
I’m not yet sure exactly what happened but it is somehow related to the macOS Shortcut’s app scripting interface. Apparently something must have changed but only in some very specific scenario.
I know I’ve said it before but it bears repeating: not only is BTT one of the best pieces of software I’ve ever bought (in terms of both functionality and value over time) but the support and responsiveness is second to none.
@Andreas_Hegenberg where can I donate to buy you a coffee?!
Thank you! You already bought me a coffee when you purchased your license, so all good! ![]()
Ok well I’ll just buy every Mac user in my life a license for Christmas. Sincerely, thank you so much for your time on this issue.
Potentially unrelated, but some adjecent weirdness that I figure might be worth sharing:
Since I blew out all of my script-related triggers (I did take a backup but a lot of them were old so I decided to start from scratch now that BTT is working for me again) I started creating some new ones using the BTT inline editor. I would get “Syntax Error” for everything, even very simple scripts that I knew were valid. So I opened the macOS Script Editor and the same simple scripts wouldn’t run/compile there either. No error, no feedback at all, just unresponsive buttons.
I searched around and found another user with a similar issue that solved it by copying the file “Applescript.component” from \System\Library\Components to \Library\Components (for me the latter was empty) which solved the issue in both macOS Script Editor and BTT inline editor. ![]()
oh that most definitely was causing the crash! Do you have any idea what happened to that file? How did you figure this out?
I’ve never touched that folder, didn’t even know about Applescript.component as a concept. I only figured it out because Applescripts were behaving oddly in both BTT and Script Editor and I searched around until I found this thread
very interesting, I'll investigate a bit! Great you found this, might save me some future headaches
//edit: in general it is fine if there is no Applescript.component in /Library/Components (I don’t have one either on any of my systems), but I assume for some reason your /System/Library/Components is not accessible (might be some weird macOS bug). The library folders are usually searched in this order System Library => All Users Library => User Library, so by copying it to your “All Users” Library folder you might have worked around the (very weird) issue.