I was aware of the potential web store deployment delay, but I guess I
On Thursday, November 15, 2012 5:35:22 PM UTC-7, Rob wrote:
> It is the trailing slash indeed. Strange that the Chrome team changed such
> I wrote a blog post about my journey and the solution, I hope it helps
> On Wednesday, November 14, 2012 12:45:55 AM UTC, Hans wrote:
>> Interestingly, though, removing the preceding slash yields an "Invalid
>> Also just tested again WITH leading slashes against Chrome 25.0.1324.0
>> I would try to elevate this, but this bug is already in the Chrome
>> On Tuesday, November 13, 2012 4:31:50 PM UTC-7, Zane Claes wrote:
>>> Apparently the bug has to do with the preceding slash. Before, both
>>> On Tuesday, November 13, 2012 7:24:32 AM UTC-8, Rob wrote:
>>>> Same problem here...
>>>> I've been trying to figure out what causes this bug for about an hour
>>>> Canary (25.0.1323.1 canary) works just fine with a freshly updated
>>>> I've tried to change the path to the 'default_icon' to various
>>>> It seems that this bug is in Chrome and it's been there for about 3
>>>> Dear Chrome, get well soon!
>>>> Sincerely Yours,
>>>> On Thursday, October 25, 2012 5:53:35 PM UTC+1, Hans wrote:
>>>>> A small number of users of my extension are getting the following
>>>>> *Package is invalid. Details: 'illegal path (absolute or relative
>>>>> 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
>>>>> I could not reproduce the issue on v24.0.1306.1 canary. In fact,
>>>>> What are the rules with respect to the format of extension file
>>>>> Thanks for any insight you may be able to offer.
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.