Re: Issue 151299 in chromium: Component v2 app can't launch from application_launcher::OpenApplication

[chro...@googlecode.com]

Updates:
Status: Assigned
Labels: Feature-Apps

Comment #2 on issue 151299 by benw...@chromium.org: Component v2 app can't
launch from application_launcher::OpenApplication
http://code.google.com/p/chromium/issues/detail?id=151299

From bshe@: One more observation. I was somehow able to launch an app
container today (without any code change, just sync to ToT) after a
rebuild. Then I load the unpacked extension from chrome://extensions, open
the container again. Then remove the unpacked app from chrome://extension
and try to launch it again. It doesn't work anymore. I also tried to launch
it from the app list. It doesn't work either.

I just built chrome os on linux with your patch and it is working for me as
expected.

As your manifest has a key which will always cause it to have the same ID,
I'd say loading this unpacked and then removing it is probably screwing
something up. Perhaps you shouldn't be able to install it as an unpacked
extension in the first place, as there is already an extension installed
with the same ID.

I'll have a look at the code to find out what is happening.

[chro...@googlecode.com]

Comment #3 on issue 151299 by b...@chromium.org: Component v2 app can't

launch from application_launcher::OpenApplication
http://code.google.com/p/chromium/issues/detail?id=151299

I see. It's definitely a problem associated with removing the unpacked app.
It screw something up. I tried launch chrome in a fresh user data dir and I
can launch the app as expected.

[chro...@googlecode.com]

Comment #4 on issue 151299 by b...@chromium.org: Component v2 app can't

launch from application_launcher::OpenApplication
http://code.google.com/p/chromium/issues/detail?id=151299

Looks like the problem was in PathToUserDataDir/user/Preferences

Normally, it should have something like this:
"obklkkbkpaoaejdabbfldmcfplpdgolj": {
"active_bit": true,
"events": [ "app.runtime.onLaunched" ]
}
After I removed the unpacked version, it changed to something like this:
"obklkkbkpaoaejdabbfldmcfplpdgolj": {
"active_bit": true
},

The "events" field got removed.

[chro...@googlecode.com]

Updates:
Cc: a...@chromium.org

Comment #5 on issue 151299 by benw...@chromium.org: Component v2 app can't

launch from application_launcher::OpenApplication
http://code.google.com/p/chromium/issues/detail?id=151299

I had a quick play with this, and found that if you have an extension
installed, and install an unpacked extension with a key forcing to the same
id, the original extension seems to be removed.

We could change it to give an error when you install the new extension, but
the current behavior seems like it would be useful for e.g. to override a
component extension during development.

Are you getting problems even after removing the unpacked extension and
restarting Chrome?