New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 671521 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

"Failed to parse extension manifest." appears in the first few lines of /home/chronos/user/log/chrome

Project Member Reported by satorux@chromium.org, Dec 6 2016

Issue description

Chrome Version       : ToT
OS Version: 
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5:
  Firefox 4.x:
     IE 7/8/9:

What steps will reproduce the problem?
1. Login

What is the expected result?

No log spam

What happens instead of that?

The following always appears in  /home/chronos/user/log/chrome

[796:796:1121/224524:ERROR:component_loader.cc(158)] Failed to parse extension manifest.

I'm curious what is failing here.



 
Owner: fukino@chromium.org
Status: Started (was: Untriaged)
Reading webstore_widget's manifest file is failing.
I'm looking into what causes this.
Ah you were faster. I added some logging and got:

[8300:8300:1206/163631.970222:ERROR:component_loader.cc(173)] Failed to parse extension manifest.
[8300:8300:1206/163631.970504:ERROR:component_loader.cc(174)] @@ name: Chrome Web Store Gallery
[8300:8300:1206/163631.970552:ERROR:component_loader.cc(175)] @@ description: An app that shows a filtered list of extensions from Chrome Web Store. Extensions in the list can be installed directly from the app.

manifest_contents was empty.
Looks that the manifest contents aren't included in the resource file?

% grep 'App for showing Chrome Webstore Gallery widget' out_kevin/Release/resources.pak
%


Project Member

Comment 4 by bugdroid1@chromium.org, Dec 7 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/27d65fa315b9eaa62db39ab9f2244e27d54377a9

commit 27d65fa315b9eaa62db39ab9f2244e27d54377a9
Author: fukino <fukino@chromium.org>
Date: Wed Dec 07 04:44:37 2016

Add chrome_apps_resources.pak to resources.pak.

webstore_widget extension, which is a part of chrome_app_resources.pak, was not
included in resources.pak. It resulted in "Failed to parse extension manifest."
error.
chrome_app_resources.pak was added in
https://codereview.chromium.org/1103943003/diff/140001/chrome/chrome_repack_resources.gypi,
but it was included in resources.pak only in GYP build.
Doing the same for GN build fixes the issue.

BUG= 671521 
TEST=boot Chrome OS and confirm that "Failed to parse extension manifest.' is not observed.

Review-Url: https://codereview.chromium.org/2556443003
Cr-Commit-Position: refs/heads/master@{#436862}

[modify] https://crrev.com/27d65fa315b9eaa62db39ab9f2244e27d54377a9/chrome/chrome_paks.gni

Status: Fixed (was: Started)
Cc: oka@chromium.org yamaguchi@chromium.org mtomasz@chromium.org
 Issue 671514  has been merged into this issue.

Comment 7 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

Comment 8 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 9 by dchan@google.com, May 30 2017

Labels: VerifyIn-60
Labels: VerifyIn-61

Comment 11 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment