kestrove/kestrove-desktop
2
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases 1 Wiki Activity

Trust the Chrome Web Store extension (pmhfoafjoogobhfadaicklhkldgnafmk)
ci / build (ubuntu-22.04) (push) Canceled after 0s
Details
ci / build (windows-2025) (push) Canceled after 0s
Details
ci / deny (push) Canceled after 0s
Details

Browse Source 
The store build has its own id, so the native-messaging manifest refused it
and the extension reported the app as not running. Chrome now allows the
store id and the unpacked development id, in the NSIS hook and in both
install scripts; --chrome-id / -ChromeId take a list.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
sami
2026-10-30 07:21:09 +04:00
co-authored by Claude Opus 5.5
parent 7b61a4851b
commit 95ce03ba06
4 changed files with 20 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
native-messaging/README.md
+4 -3
View File
@@ -1,9 +1,10 @@
# Native messaging manifests
`install.sh` (Linux, macOS) and `install.ps1` (Windows) fill in the placeholders and register the
manifests for the current user. Default ids are the development ones: the unpacked Chrome build is pinned
to `kogapfibnnpeapfcjkkpgjddbhnjfein` by the manifest key in kestrove-browser, Firefox uses
`[email protected]`. Pass `--chrome-id` / `-ChromeId` for a Web Store build.
manifests for the current user. Chrome allows two ids by default: the Chrome Web Store build
(`pmhfoafjoogobhfadaicklhkldgnafmk`) and the unpacked development build, pinned to
`kogapfibnnpeapfcjkkpgjddbhnjfein` by the manifest key in kestrove-browser. Firefox uses `[email protected]`.
Pass `--chrome-id a,b` / `-ChromeId a,b` to allow other ids instead.
```bash
native-messaging/install.sh # every browser with a profile dir, host from target/