.crx file fails to load through --load-component-extension

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run Chrome from the command line specifying --load-component-extension 
pointing to valid .crx file

For example (this was pulled from the chromedriver.log):  /Applications/Google 
Chrome.app/Contents/MacOS/Google Chrome 
--load-component-extension=/Users/meghanmcqueeney/code/yw-6350_Load_ChromeDriver
_Extensions/Backend/features/support/../../../Browser/extension/unpacked/test/ch
rome.crx --ignore-certificate-errors --remote-debugging-port=56136 
--no-first-run --enable-logging --logging-level=1 
--user-data-dir=/var/folders/68/7dczxqcj6_99qg96kh_jk3lr0000gn/T/.org.chromium.C
hromium.kJGYgC 
--load-extension=/var/folders/68/7dczxqcj6_99qg96kh_jk3lr0000gn/T/.org.chromium.
Chromium.ONYVGn/internal --ignore-certificate-errors --metrics-recording-only 
data:text/html;charset=utf-8

After attempting to load get error (seen either in the chromedriver.log or 
after running from the command line):
[0.356][DEBUG]: devtools request: http://127.0.0.1:56136/json/version
[0.357][DEBUG]: devtools request failed
[58727:1799:0828/165609:ERROR:component_loader.cc(158)] Could not load 
extension from ''. Manifest file is missing or unreadable.
[0.408][DEBUG]: devtools request: http://127.0.0.1:56136/json/version

The same extension loads fine if I drag and drop into a running Chrome Browser. 
This was reproduced building the CRX using pack extension from the browser or 
from the command line. I have attached both a log and the crx file.

What version of the product are you using? On what operating system?
ChromeDriver = 2.2
Chrome = 29.0.1547.57
OS = Max OS X 10.8.4

Please attach chromedriver.log to your bug report if possible.

Original issue reported on code.google.com by meg...@yesware.com on 28 Aug 2013 at 9:17

Attachments:

• chrome.crx
• chromedriver.log

[GoogleCodeExporter]

load-component-extension requires an unpacked extension, not a crx

Original comment by kkania@chromium.org on 29 Aug 2013 at 2:41

• Changed state: Closed

[GoogleCodeExporter]

Then something else is wrong because using an unpacked extension directory 
causes Chrome to crash. Is there documentation on this flag?  I don't see it 
here (the doc that is provided in the wiki):
http://peter.sh/experiments/chromium-command-line-switches/

Original comment by meg...@yesware.com on 29 Aug 2013 at 3:00

[GoogleCodeExporter]

Yes, that flag is not well supported and often crashes. we'll fix the other bug 
for you.

Original comment by kkania@chromium.org on 29 Aug 2013 at 4:57

[GoogleCodeExporter]

Original comment by samu...@chromium.org on 21 Feb 2015 at 12:26

• Changed state: Fixed