Forum Discussion

Former Member's avatar
Former Member
4 years ago

Can't set the Quick Access keyboard shortcut to the old one

I noticed that the Quick Access keyboard shortcut was no longer working with the 1Password 8 Mac beta. I checked the preferences and it seems to have been changed to Shift-Cmd-Space.

Being used to using Opt-Cmd-\ I have been trying to reset it. When I try, though, it takes my Opt-Cmd-\ and turns it into Cmd-C which means quick access suddenly took over the system Copy shortcut.

I'm not sure why, but the preferences refuse to let me set it to Opt-Cmd-\

Any idea why?

1Password Version: 8.7.0 Build 80700049
Extension Version: 2.3.1
OS Version: macOS 12.2.1

betas

3 Replies

  • Dayton_ag's avatar
    Dayton_ag
    Icon for 1Password Team rank1Password Team
    4 years ago

    Hey @Ostrowalker, ahhh, that makes sense! I'm glad you were able to track down the conflicting shortcut - thanks for sharing! 😃

  • Former Member's avatar
    Former Member
    4 years ago

    Thanks for trying it yourself.

    Indeed I discovered that the Alfred App recently introduced the shortcut into it's Universal Actions trigger. But it was difficult to determine because it would only activate in certain scenarios, like having text selected.

    I've remapped the Alfred Shortcut to something else and now 1Password is behaving as expected.

    Cheers,
    Joshua.

  • Dayton_ag's avatar
    Dayton_ag
    Icon for 1Password Team rank1Password Team
    4 years ago

    Hi @Ostrowalker, thanks so much for writing in! That's definitely odd behavior - I just gave this a shot on my personal Mac and was able to change the shortcut from the default of Shift-Command-Space to Option-Command-\ and it took fine on my machine, and I was able to launch and hide Quick Access using that shortcut.

    Is it possible that another program on your machine is now making use of the Option-Command-\ shortcut?

    Let me know what you find, and we can keep the ball rolling from there - we can also move this to email so we can look deeper into some logs to see if they help us sort out the issue. 😄