Web Clipper with macOS Sequoia missing default_locale

[jmantn]

First, search the help docs and this forum. Maybe your question has been answered! The debugging steps can help, too. Still stuck? Delete this line and proceed.

What I’m trying to do

In the latest version of macOS with the latest version of Obsidian for Mac through the website, inside the app checked for updates, none found, version: About Obsidian
Version 1.8.4 (Installer 1.7.7) and the latest version of the Obsidian Web Clipper through the Mac App Store saved clippings do not save to any vault. All Vaults are syncing with iCloud.

I have my Obsidian Vault Open and within Safari will try and save a web clipping and I see no errors but no files are added to Obsidian. Within Safari > Settings > Extensions > Obsidian Web clipper there is this message: * Unable to find default_locale in “_locales” folder.

That’s the only error I can see.

On iOS and iPadOS this is working as expected.

Things I have tried

For the Web Clipper Settings > General Settings > Vault > I have tried with the setting blank, with the setting Resources/Clippings, and with the name of my Vault and it’s Clippings folder and nothing is working and I didn’t see any specific resources on this.

[jmantn]

I noticed later that it wasn’t asking me to open in Obsidian on macOS when saving.

Later I realized the issue is the Web Clipper does not function correctly within a Safari Tab Group. If in the default Safari profile it works, if in a Tab Group it does not work.

This seems to be a bug.

[runnermule]

A possibility. I don’t use Safari Tab Group so I cannot test. By default access to locale is blocked by macOS and has to be allowed for each app. Idea: Open System Settings from the upper left Apple icon. Choose Apple menu > System Settings, click Privacy & Security in the sidebar, then click Location Services. Scroll down the list to find Obsidian, then toggle location services on.

As an aside, after I allowed location services in System Settings the Error for Obsidian Web Clipper persists in the Extensions window of Safari. Might need a restart, or might not really be a fix.