Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E2E: CRX hash pub key #157

Open
gbarkhatov opened this issue Dec 23, 2024 · 0 comments
Open

E2E: CRX hash pub key #157

gbarkhatov opened this issue Dec 23, 2024 · 0 comments
Assignees

Comments

@gbarkhatov
Copy link
Contributor

When we try to download the extension, we use it's Chrome Store id.
But when accessing the extracted extension, the inner id is different.

Currently, we use EXTENSION_CHROME_INNER_IDS. But it also means that if we download the new verions of the extension, the inner id is different.

To get the inner id we now manually go to the Chrome extension tab inside the Playwright and update the IDs.

We need to parse the CRX header to programmatically derive the true extension ID. That’s how Chrome figures out the hashed ID we see in chrome://extensions. Once we do that, we won’t need to hardcode or guess the “inner extension ID” in our config.

  1. We write our own solution of getExtensionIdFromCrx if it is simple.
  2. We rely on the third-party solution, some sort of crx related npm library
  3. less desired We write a Playwright test that manually goes to the chrome extensions and grabs the extension id
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant