extention is not loadable from the command line
Reported by
d...@pinterest.com,
Feb 23 2018
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36 Steps to reproduce the problem: 1. /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --load-extension="~/Library/Application\ Support/Google/Chrome/Default/Extensions/cflchafndefoljnhhholeekfpgmbphaf/1.51_0/" --profile-directory="Profile 0" nytimes.com 2. error: Failed to load extension from . Manifst file is missing or unreadable. What is the expected behavior? What went wrong? I don't know why it tries to locate the extension from '.'. when I go to that extension directory. the msg is gone but a new error msg saying I cant load some js in that extension dir. WebStore page: Did this work before? N/A Chrome version: 64.0.3282.167 Channel: n/a OS Version: OS X 10.13.3 Flash Version:
,
Feb 25 2018
If you use quotes there's no need to escape the space character in the extension path.
,
Feb 26 2018
I don't think that matters as without quote, I got the same error
,
Feb 26 2018
Able to reproduce this issue by following steps in comment#0 on 64.0.3282.167 using Mac 10.13.3. i.e; On pasting /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --load-extension="~/Library/Application\ Support/Google/Chrome/Default/Extensions/cflchafndefoljnhhholeekfpgmbphaf/1.51_0/" --profile-directory="Profile 0" nytimes.com in terminal seeing "Failed to load extension from: . Manifest file is missing or unreadable." error. This issue is seen from M-60. Hence considering this issue as Non-Regression and marking as Untriaged. Thanks!
,
Feb 28 2018
any updates?
,
Mar 5 2018
As per comment#4 Changing the status to Untriaged. Thanks!
,
Mar 5 2018
First sanity check: does the path exist? i.e., is the manifest located at ~/Library/Application\ Support/Google/Chrome/Default/Extensions/cflchafndefoljnhhholeekfpgmbphaf/1.51_0/manifest.json?
,
Mar 5 2018
@rdevlin. yes. it exists. The msg i got says it looks at `.` instead of this path
,
Mar 5 2018
It looks like the problem is that the load-extension commandline flag doesn't accept ~/ paths. Absolute paths (/path/to/extension) work fine, and relative paths (./extension) work as well, but paths with the home character fail. This should be something we can fix. This repros with something as simple as <path to chrome> --load-extension=~/<path to extension> (i.e., the additional commandline arguments are unnecessary) dbertoni@, this could be another good one for you to look into.
,
Mar 5 2018
And in the meantime, dbao@, just supplying an absolute path should work. :) Thanks for reporting the bug!
,
Mar 19 2018
I've verified the same behavior with the --user-data-dir command line flag, so it seems Chrome generally doesn't do tilde shell expansion.
,
Apr 2 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a38320bf6bcebdb7558a28f30edecd8d1545f9c9 commit a38320bf6bcebdb7558a28f30edecd8d1545f9c9 Author: David Bertoni <dbertoni@chromium.org> Date: Mon Apr 02 20:38:07 2018 Resolve a leading ~ in extension loading path to the user's home dir. Bug: 815060 Change-Id: I358fca7bfeb19ef035703f37318f7eb0c90d7015 Reviewed-on: https://chromium-review.googlesource.com/976550 Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Devlin <rdevlin.cronin@chromium.org> Commit-Queue: David Bertoni <dbertoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#547512} [modify] https://crrev.com/a38320bf6bcebdb7558a28f30edecd8d1545f9c9/chrome/browser/extensions/unpacked_installer.cc [modify] https://crrev.com/a38320bf6bcebdb7558a28f30edecd8d1545f9c9/extensions/browser/path_util.cc [modify] https://crrev.com/a38320bf6bcebdb7558a28f30edecd8d1545f9c9/extensions/browser/path_util.h [modify] https://crrev.com/a38320bf6bcebdb7558a28f30edecd8d1545f9c9/extensions/browser/path_util_unittest.cc
,
Apr 2 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by susan.boorgula@chromium.org
, Feb 25 2018