How to change chrome packaged app id Or Why do we need key field in the manifest.json?

by

Once uploaded to the Chrome Web Store, your extension ID is fixed and cannot be changed any more.

The ID is derived from the .pem file that was created the first time you (or the Chrome Web Store) packed the extension in a .crx file. When you load an extension in “unpacked mode”, an ID is automatically generated in an unpredictable way. The only way to control the extension ID during development is by setting the "key" field in the manifest file, as the documentation suggests.

When you have already published the extension in the Chrome Web Store, then you can easily get the value of this "key" field using the Chrome Extension Source Viewer. After installing the extension, go to your Chrome web store details page and click on the CRX button to view the source. When the Chrome Extension Source viewer has loaded the extension, it will display the key in the console, which can directly be copy-pasted to your manifest.json:

Screenshot: Public key (paste into manifest.json to preserve extension ID) crxviewer.js:528 "key": "....", crxviewer.js:529 Calculated extension ID: jifpbeccnghkjeaalbbjmodiffmgedin

If you have not published your extension, or you do not want to use the Chrome Web Store, then you need to generate a private key first.

  1. Go to chrome://extensions/ and enable Developer mode.
  2. Click on “Pack extension…”, select your app/extension’s directory and confirm.
    Now you’ve got a .crx file and a .pem file. Back up the private key (.pem file)!
  3. The extension mentioned can be used to get the same information. Alternatively, visit the online demo at https://robwu.nl/crxviewer/ and select the crx file you’ve just created (again: just open the console to see the “key” and extension ID).

When you’re ready to submit your app/extension to the Chrome Web Store, follow the following steps:

  1. Create a zip file containing your extension (important: manifest.json must be at the root, i.e. “directory/manifest.json” is bad, “manifest.json” is good).
    • Add the .pem file as key.pem!
      (this is necessary to preserve the extension ID)
  2. Upload the extension to the Chrome Web Store (without the “key” field in manifest.json, the CWS will reject any upload that contains a “key” field).

For subsequent updates, “key.pem” should not be added to the zip file, because the Chrome Web Store does not need it any more.

More Related Contents:

  1. chrome extension mv3 – Modularize service worker js file
  2. How can I enable my chrome extension in incognito mode?
  3. How do I import scripts into a service worker using Chrome extension manifest version 3?
  4. Chrome Console SameSite Cookie Attribute Warning
  5. How to access the webpage DOM rather than the extension page DOM?
  6. Disabling Chrome cache for website development
  7. Chrome Extension Message passing: response not sent
  8. “CAUTION: provisional headers are shown” in Chrome debugger
  9. How do you inspect the web inspector in Chrome?
  10. How to save CSS changes of Styles panel of Chrome Developer Tools?
  11. Detect Chrome extension first run / update
  12. Chrome stalls when making multiple requests to same resource?
  13. Disable developer mode extensions pop up in Chrome
  14. Modifying the built-in newtab page
  15. Chrome Extension Content Script on https://chrome.google.com/webstore/
  16. Is it possible to run Google Chrome in headless mode with extensions?
  17. Using ECMAScript 6
  18. How to download a CRX file from the Chrome web store for a given ID? [closed]
  19. Making HTTP Requests using Chrome Developer tools
  20. Communicating between a Chrome packaged app and a Chrome extension?
  21. How to access the webpage DOM/HTML from an extension popup or background script?
  22. Remote Debugging for Chrome iOS (and Safari)
  23. Disable chrome download multiple files confirmation
  24. Prevent chrome.notifications API from hiding my notification after a few seconds
  25. Chrome developer tools workspace mappings
  26. Chrome Dev Tools: How to trace network for a link that opens a new tab?
  27. Run script each time Chrome extension icon clicked
  28. How to block a URL in Chrome’s developer tools network monitor
  29. Chrome remote debugging doesn’t work with IP
  30. Link to chrome:// url from a webpage

Leave a Comment