Unable to exit Restricted Mode on macOS 26 (Obsidian 1.12.7)

Bug reports
1

Steps to reproduce

  1. Create a brand new local vault.
  2. Go to Settings → Community plugins.
  3. Click Turn on community plugins.
  4. Click Turn on and reload.
  5. After reload, open Settings → Community plugins again.

Did you follow the troubleshooting guide? [Yes]

Expected result

Restricted Mode is disabled and Community Plugins become available.

Actual result

Obsidian reloads and returns to the vault, but Restricted Mode remains enabled.
This happens even with a brand new local vault.

Environment

SYSTEM INFO:
Obsidian version: 1.12.7
Installer version: 1.12.7
Operating system: Darwin Kernel Version 25.5.0: Mon Apr 27 20:38:00 PDT 2026; root:xnu-12377.121.6~2/RELEASE_ARM64_T8103 25.5.0
Login status: not logged in
Language: en
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: on
RECOMMENDATIONS:
none

Additional information

Reproduced with a brand new local vault.
Also reproduced after resetting ~/Library/Application Support/obsidian.
Official notarized Obsidian 1.12.7.
No errors in Developer Console.
View → Force Reload works.
Developer: Reload app without saving works.
Turn on and reload reloads the app, but Restricted Mode remains enabled.
localStorage.getItem(‘enable-plugin-’ + this.app.appId) returns false.
Manually setting it to true works temporarily:
localStorage.setItem(‘enable-plugin-’ + this.app.appId, ‘true’)
but after restarting/reloading it is automatically reset to false.
I found a similar forum topic (“Unable to turn any community plugins on in a new vault”), but that issue was caused by an incomplete plugin installation due to a firewall. My issue occurs before any community plugin can be enabled and is reproducible with a brand new local vault.

2

Are the vaults stored in a cloud folder like iCloud (or a location that could be controlled by one, like Documents)? And if so, have you set the vault folder to “Keep downloaded”?

3

The vault is stored in a completely local folder, not in iCloud, Dropbox, OneDrive, or any other cloud-synced location.

To rule that out, I also created a brand new vault in a local folder outside Documents (for example, ~/ObsidianTest), and the issue is exactly the same.

So this does not appear to be related to cloud storage or Files On-Demand.