You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hey, i hope everyone is doing well. ive noticed that the option command i devtools keybind on vesktop/macOS has been broken since i've been using vesktop (~8 months), it works on desktop discord with vencord. it works on vesktop when you click view in the menu bar and then do the keyboard shortcut, but it does not work when you option command i without the view menu selected. this screen recording showcases the issue. ive been told its a system issue but multiple people have said in #vencord-support that it happens to them too, and ive restored my mac to factory settings in the past and it still persists with vesktop as the only software installed on the mac aside from the complete default apple software that comes preloaded with macOS. giving vesktop screen recording, accessibility, and input monitoring perms followed by fully quitting & re launching the app doesn't fix it either (which would ensure that macOS is not preventing vesktop's keybinds from functioning), and i don't have any conflicting keybinds on the mac. any further investigation would be greatly appreciated!
Discord Account
<@1208425348312596550>
Operating System
macOS 15.1.1
Linux Only ~ Desktop Environment
No response
Package Type
n/a
What happens when the bug or crash occurs?
hey, i hope everyone is doing well. ive noticed that the option command i devtools keybind on vesktop/macOS has been broken since i've been using vesktop (~8 months), it works on desktop discord with vencord. it works on vesktop when you click view in the menu bar and then do the keyboard shortcut, but it does not work when you option command i without the view menu selected. this screen recording showcases the issue. ive been told its a system issue but multiple people have said in #vencord-support that it happens to them too, and ive restored my mac to factory settings in the past and it still persists with vesktop as the only software installed on the mac aside from the complete default apple software that comes preloaded with macOS. giving vesktop screen recording, accessibility, and input monitoring perms followed by fully quitting & re launching the app doesn't fix it either (which would ensure that macOS is not preventing vesktop's keybinds from functioning), and i don't have any conflicting keybinds on the mac. any further investigation would be greatly appreciated!
What is the expected behaviour?
devtools to open
How do you recreate this bug or crash?
option command i while vesktop is focused
Debug Logs
Request Agreement
The text was updated successfully, but these errors were encountered: