Opening Dash.app Clears Hotkey Configured in Dash Workflow

benbscholz commented 3 years ago

To reproduce:

Ensure Dash.app is not running.
Open Alfred preferences and configure the Dash workflow hotkey to ⇧⌘Space (note: any combination should trigger the bug).
Open Dash.app and wait ~5 seconds.

Expected Result: The hotkey configured in the Dash workflow will remain ⇧⌘Space (or the combination saved in Step 2). Actual Result: The hotkey configuration will be cleared.

Environment:

Dash.app: Version 6.0.7 (Build 980)
Alfred.app: Version 4.3.4 [1229]

It’s not clear to me whether this is an issue with Dash.app or the Dash Alfred workflow, but it seemed like this was the most sensible place to report the issue. If you would like me to file this issue elsewhere, let me know.

I’ve provided a video demonstrating the issue. The video was recorded on macOS 12.0 Beta (21A5284e) but the issue is reproducible on macOS 11.x. (In the video, I open Dash.app via Alfred though it should be noted that the hotkey configuration is cleared no matter how Dash is opened - by double-clicking Dash.app in the Applications folder, for instance).

https://user-images.githubusercontent.com/599905/127184346-9e31f5ef-d293-4015-9f46-bc7f19860a1a.mov

Kapeli commented 3 years ago

I'm not able to reproduce the issue. What I did:

Imported the Alfred workflow from Dash's Preferences > Integration
Quit Dash
Set the hotkey in Alfred
Launch Dash
Waited a few minutes and the hotkey was not cleared

Do you have multiple versions of Dash on your Mac by any chance?

benbscholz commented 3 years ago

@Kapeli I only have one version of Dash.app (installed in /Applications) that I downloaded from here. (I just deleted it and re-installed a fresh version though I didn't clear out preferences/license key from Application Support or wherever they live).

I removed the workflow from Alfred & quit Alfred. After re-importing the workflow from Dash's Preferences > Integration, I still experience the problem.

Thanks for trying to reproduce. There must be something else different about my setup - short of a fresh macOS install, I'm not sure how to figure out what it might be (though if I do set up a machine from scratch in the near future and still encounter the issue, I'll let you know).