After updating to Ventura on my Mac, I am finding Hookmark to be randomly invoking itself when working on documents (i.e. without any keyboard shortcuts or other requests being made). This is naturally very distracting and I’d be grateful for some assistance as it is making Hookmark unusable.
I’ve got the same problem and can’t get rid of it. Hookmark ist constantly invoking itself on Ventura.
I already deleted Hook, installed Hookmark4 (and also tried with Hookmark5), it still remains invoking itself every 55 sec.
Any idea how to fix this?
Thanks for your advice, but this also doesn’t work.
I deleted every instance, every DMG, even the lib folder (backup on an external drive), emptied the trash. But nothing changed, after downloading and installing a new version the app still keeps on invoking itself, which makes it pretty useless – I’m always interrupted in whatever I’m doing and have to get rid of the hookmark-window.
@langley, @dirk and anyone else: if you are (still) seeing this and are using Trickster app would you please let us know if quitting Trickster solves the problem? This explains at least some cases of this problem. Maybe all of them. We can also reproduce it on Monterey and Ventura when Trickster is running.
So for now the solution would be to not run Trickster and Hookmark at the same time.
If you are experiencing this and it is not due to Trickster, then please consider whether you have any automation ( via Keyboard Maestro, AppleScript, or anything) that might be interacting with Hookmark. You can see the processes running on in your account using Activity Monitor ; or all processes via sudo ps -ax in Terminal app.
To make this topic easier for others to find, I’m renaming this topic from “Hookmark randomly invoking itself on Ventura” because it’s unlikely Hookmark is invoking itself in this case (the only case Hookmark has a UI change independently is in menu bar window [not the context window], but customers have turned off that feature). Also it’s not just Ventura. And it doesn’t seem random but regular. so “Hookmark context window popping up regularly”.
@LucB Yes, after quitting Trickster Hookmark now works fine! Thank you!
(I tried then one more step: After quitting and trying to restart Trickster both apps froze, I had to quit them via „Aktivitätsanzeige“ (activity monitor?), after that I startet first Hookmark, then Trickster and now they both work together without popping up the context window).
Hi, @dirk. Trickster developer here. Trickster itself didn’t change in a while, certainly not its connection to Hookmark but Hookmark itself changed (and maybe how macOS handles thing). We’ll take a look at how it invokes Hookmark and what can be done to fix this problem. @LucB and I are in contact about it. What’s your environment (version off macOS, version of Trickster and Hookmark)? When did it start to happen?
Interesting! Yes, I do have Trickster installed, but it hasn’t yet become part of my regular workflow—I installed it thinking it looked useful, but haven’t spent the time to integrate it. Having just clicked on the menu bar icon it popped up with a menu asking me to locate Hook. I then chose Hookmark from the list of applications. I will test to see whether that solves the problem, and if it doesn’t will try quitting trickster
@bchend here can reproduce the issue with Setapp and standalone versions of Trickster 3.9 and Hookmark 4 and Hookmark 5 using 12.6 (she’ll try 12.6.2) and Ventura.
I cannot reproduce the issue. Have only tried macOS 12.6.2 (21G320), Hookmark 5 with latest Setapp version of Trickster (3.9).
Nothing changed in Hookmark 4 that vs. 3.8 regarding applicationShouldHandleReopen code. We know that Hookmark is on the receiving end of an event that opens window, but we do not currently know where that event comes from.
We tried disabling our AppleScript method that can bring up the window, and this did not prevent the problem (to our surprise).
It looks like there is some other variable involved . I don’t know what. I couldn’t see a relevant Trickster preference to explain the diff.
I think I figured it out but I may need your help to confirm.
I think it’ll happen to customers whose app name for Hookmark is not “Hook”.
I’m not sure how new downloads are called but my “upgraded from Hook” version was still called Hook.
When I manually renamed it from Hook to Hookmark, I got the “Locate Hook” dialog popup.
@LucB@langley@dirk Can you confirm that your application name is something other than “Hook” in Finder when it fails?