The issue occurs when obsidian is running but either:
- the obsidian window is minimized (⌘-M)
- the obsidian window is closed (⇧-⌘-W)
In that situation, after having focused Obsidian (using ⌘-tab):
- pressing ⌘-N has no effect (the File menu flashes but nothing happens)
- actually clicking File > New Note produces an error window:
⇧-⌘-N / “File > New Note to the Right” has the same effect
1 Like
I can reproduce.
With only Sandbox open:
- If the Sandbox is minimized to the dock, ⌘+N does nothing (but the File menu flashes).
- If the Sandbox is minimised, File>New Note shows the JavaScript error.
If no vaults are open but Obsidian is running and the focused app:
- ⌘+N does nothing (but the File menu flashes).
-
File>New Note shows the JavaScript error.
I never have Obsidian running with all vaults minimized or closed so have never seen this before. It’s understandable with no open or focused vault that Obsidian doesn’t know where to put a new note, but the vault switcher, at least, should show up.
@masklinn, could put post your debug info (⌘+P>Show debug info) just to finish out your bug report? Thanks. Here’s mine:
macOS 12.6.2, Sandbox
SYSTEM INFO:
Obsidian version: v1.1.9
Installer version: v1.1.9
Operating system: Darwin Kernel Version 21.6.0: Sun Nov 6 23:31:13 PST 2022; root:xnu-8020.240.14~1/RELEASE_ARM64_T6000 21.6.0
Login status: logged in
Catalyst license: insider
Insider build toggle: on
Live preview: on
Legacy editor: off
Base theme: dark
Community theme: none
Snippets enabled: 0
Restricted mode: on
RECOMMENDATIONS:
none
1 Like
I can also reproduce this.