New issue
Advanced search Search tips

Issue 661145 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Extension in developer mode lost after restart

Reported by christop...@gmx.com, Nov 1 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.72 Safari/537.36 Vivaldi/1.5.652.4

Steps to reproduce the problem:
1. install an unpacked extension in developer mode with a certain key
2. close Chrome
3. change this key in extension's manifest
4. open Chrome
5. close Chrome
6. change this key back to the original one
7. open Chrome
8. restart at will

What is the expected behavior?

What went wrong?
It's gone and will always be gone as soon as you restart no matter how often you reinstall it.

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 54.0.2840.72  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0

I found this when I tried to develop an extension in two "channels" (stable and beta) providing both via the Chrome Web Store (latter one to a distinct closed group of testers).
 
This happens due to a duplicate entry in Secure Preferences file. You will end up with two entries naming the same folder with two IDs and one of them can't load since the extension ID doesn't exist anymore, which seems to cause the other one to disappear from UI as well (they are still both in file).
Components: Platform>Extensions
Labels: -Hotlist-Interop
Cc: kkaluri@chromium.org
Labels: Needs-Feedback
christoph142@, In order to triage this issue could you please explain on how to change the extension manifest key and if possible please provide the sample extension file.

Thank You...
Hi Kkaluri,

this simple manifest.json file will do:


{	
	"name"						: "test extension",
	"description"				: "extension for testing key issue",
	
	"version"					: "1.0",
	"key"						: "KEYGOESHERE",
	
	"manifest_version"			: 2
}

You need to log into Chrome Web Store and have two extensions in your dev cockpit. Just insert any of these keys where KEYGOESHERE is.
(The key is the "Public key" located in "More info" at the right end of your extension at https://chrome.google.com/webstore/developer/dashboard without the -----BEGIN PUBLIC KEY----- and -----END PUBLIC KEY----- part)
Project Member

Comment 6 by sheriffbot@chromium.org, Nov 10 2016

Labels: -Needs-Feedback Needs-Review
Owner: kkaluri@chromium.org
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Needs-Review TE-NeedsTriageHelp
Owner: ----
Project Member

Comment 8 by sheriffbot@chromium.org, Feb 13 2018

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment