Message from discussion
Package is invalid. Details: 'illegal path (absolute or relative with '..')
Received: by 10.224.220.136 with SMTP id hy8mr614704qab.3.1352848308744;
Tue, 13 Nov 2012 15:11:48 -0800 (PST)
X-BeenThere: chromium-extensi...@chromium.org
Received: by 10.229.75.131 with SMTP id y3ls3521794qcj.3.gmail; Tue, 13 Nov
2012 15:11:33 -0800 (PST)
Received: by 10.224.189.16 with SMTP id dc16mr8991351qab.0.1352848293076;
Tue, 13 Nov 2012 15:11:33 -0800 (PST)
Received: by 10.224.16.202 with SMTP id p10msqaa;
Mon, 12 Nov 2012 09:45:14 -0800 (PST)
Received: by 10.236.116.67 with SMTP id f43mr2416645yhh.13.1352742302755;
Mon, 12 Nov 2012 09:45:02 -0800 (PST)
Date: Mon, 12 Nov 2012 09:45:01 -0800 (PST)
From: peegee <tgtw...@gmail.com>
To: chromium-extensi...@chromium.org
Message-Id: <0f611190-dd7e-42d0-9f08-bbc0c7257ca0@chromium.org>
In-Reply-To: <db83fdb1-50e9-499b-b96f-1b53978e0ad0@chromium.org>
References: <db83fdb1-50e9-499b-b96f-1b53978e0ad0@chromium.org>
Subject: Re: Package is invalid. Details: 'illegal path (absolute or
relative with '..')
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_398_31409020.1352742302061"
------=_Part_398_31409020.1352742302061
Content-Type: multipart/alternative;
boundary="----=_Part_399_13089342.1352742302061"
------=_Part_399_13089342.1352742302061
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Same problem here - only on some chrome users. Majority are fine.
"Package is invalid. Details: 'Illegal path (absolute or relative with
'..'): '/icons/actions/1.png''.
On Thursday, 25 October 2012 12:53:35 UTC-4, Hans wrote:
>
> A small number of users of my extension are getting the following error
> message when installing it from the Web Store:
>
> *Package is invalid. Details: 'illegal path (absolute or relative with
> '..'):/images/icon_19x19_disabled.png'*
>
> This error maps to the following line in the extension's manifest file:
>
> * "default_icon": "/images/icon_19x19_disabled.png",
> *
>
> The common thread seems to be that these users are all running Chrome v
> 23.0.1271.xx.
>
> I could not reproduce the issue on v24.0.1306.1 canary. In fact, removing
> the leading slash from all icon references in the manifest file resulted in
> an "Invalid Manifest file" error upon installation of the extension.
>
> What are the rules with respect to the format of extension file references
> in the manifest, and are there any known issues related to the above error?
>
> Thanks for any insight you may be able to offer.
>
> Sincerely,
> Hans Meyer
>
------=_Part_399_13089342.1352742302061
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Same problem here - only on some chrome users. Majority are fine.<div=
><br></div><div>"Package is invalid. Details: 'Illegal path (absolute or re=
lative with '..'): '/icons/actions/1.png''.</div><div><br>On Thursday, 25 O=
ctober 2012 12:53:35 UTC-4, Hans wrote:<blockquote class=3D"gmail_quote" s=
tyle=3D"margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-le=
ft: 1ex;"><font face=3D"verdana, sans-serif">A small number of users of my =
extension are getting the following error message when installing it from t=
he Web Store:</font><div><font face=3D"verdana, sans-serif"><br></font></di=
v><div><font face=3D"verdana, sans-serif"><font color=3D"#000000" style=3D"=
background-color:rgb(255,255,255)"><b>Package is invalid. Details: 'illegal=
path (absolute or relative with '..'):/images/icon_19x19_<wbr>disabled.png=
'</b></font><br></font></div><div><span style=3D"background-color:rgb(255,2=
55,238);color:rgb(0,0,0)"><font face=3D"verdana, sans-serif"><br></font></s=
pan></div><div><font face=3D"verdana, sans-serif"><font color=3D"#000000">T=
his error maps to the following line in the extension's manifest file:</fon=
t></font></div><div><font face=3D"verdana, sans-serif"><font color=3D"#0000=
00"><br></font></font></div><div><font face=3D"verdana, sans-serif"><font c=
olor=3D"#000000"><b> "default_icon": "/images/icon_19x19_disab=
led.<wbr>png",<br></b></font></font></div><div><font face=3D"verdana, sans-=
serif"><font color=3D"#000000"><br></font></font></div><div><font face=3D"v=
erdana, sans-serif"><font color=3D"#000000">The common thread seems to be t=
hat these users are all running Chrome v</font><span style=3D"color:rgb(48,=
57,66);font-size:12px">23.0.1271.xx. </span></font></div><div><span st=
yle=3D"color:rgb(48,57,66);font-size:12px"><font face=3D"verdana, sans-seri=
f"><br></font></span></div><div><font face=3D"verdana, sans-serif"><span st=
yle=3D"color:rgb(48,57,66);font-size:12px">I could not reproduce the issue =
on v</span><span style=3D"color:rgb(48,57,66);font-size:12px">24.0.1306.1 c=
anary. In fact, removing the leading slash from all icon references in the =
manifest file resulted in an "Invalid Manifest file" error upon installatio=
n of the extension.</span></font></div><div><font face=3D"verdana, sans-ser=
if"><span style=3D"color:rgb(48,57,66);font-size:12px"><br></span></font></=
div><div><font color=3D"#303942" face=3D"verdana, sans-serif"><span style=
=3D"font-size:12px">What are the rules with respect to the format of extens=
ion file references in the manifest, and are there any known issues related=
to the above error?</span></font></div><div><font color=3D"#303942" face=
=3D"verdana, sans-serif"><span style=3D"font-size:12px"><br></span></font><=
/div><div><font color=3D"#303942" face=3D"verdana, sans-serif"><span style=
=3D"font-size:12px">Thanks for any insight you may be able to offer.</span>=
</font></div><div><font color=3D"#303942" face=3D"verdana, sans-serif"><spa=
n style=3D"font-size:12px"><br></span></font></div><div><font color=3D"#303=
942" face=3D"verdana, sans-serif"><span style=3D"font-size:12px">Sincerely,=
</span></font></div><div><font color=3D"#303942" face=3D"verdana, sans-seri=
f"><span style=3D"font-size:12px">Hans Meyer</span></font></div></blockquot=
e></div>
------=_Part_399_13089342.1352742302061--
------=_Part_398_31409020.1352742302061--