Repository navigation
fix: restore Chrome Extension ID to Web Store value (jadfnbfppmcpbfiickiolonfldkphmfb) - #32
Merged
Merged
Conversation
Replace the development key-derived ID with the ID assigned by the Chrome Web Store (jadfnbfppmcpbfiickiolonfldkphmfb). Updates manifest key field, NativeMessagingRegistrationService, BrowserHost manifest, and build-installer script so all references stay consistent. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2 tasks
pexatar
added a commit
that referenced
this pull request
May 14, 2026
Fixes Chrome extension connectivity broken in v1.0.13 due to wrong ChromeExtensionId (development ID was shipped instead of Web Store ID). Fixed in PR #32 — this bump ensures users get the corrected exe. Co-authored-by: Giuseppe Imperato <pexatar@users.noreply.github.com> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bug
Chrome extension cannot connect to PassKey Desktop.
Root cause: The commit
f7bad7fthat updatedChromeExtensionIdfrom the developmentvalue (
jmddfinmjgpgmfkiblhnjccagheadpop) to the Chrome Web Store value(
jadfnbfppmcpbfiickiolonfldkphmfb) was in branchfeat/browser-extension-store-readinessbut was added after PR #28 was merged. It was never cherry-picked to main.
PR #29 (which contained this commit) was closed instead of merged.
As a result, the v1.0.13 installer shipped
PassKey.Desktop.exethat writes the wrongChrome Extension ID into
%LOCALAPPDATA%\PassKey\native-messaging\com.passkey.host.json,causing Chrome to reject the native messaging connection.
Firefox was unaffected because its ID was correctly set in PR #28.
Fix
Cherry-pick of
f7bad7f— updates 4 files:src/PassKey.Desktop/Services/NativeMessagingRegistrationService.cs—ChromeExtensionIdconstantscripts/build-installer.ps1— manifest generationsrc/PassKey.BrowserHost/Manifests/com.passkey.host.json— dev reference manifestextensions/chrome/manifest.json—keyfield alignmentImpact
Requires a v1.0.14 installer release so users get the fixed exe.
Immediate workaround: overwrite
com.passkey.host.jsonwith the correctallowed_origins.🤖 Generated with Claude Code