Reputation: 83
I configured the update url as following:
"update_url": "https://www.myextension.host.com/updates.xml"
And the updates.xml file:
<?xml version='1.0' encoding='UTF-8'?>
<gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'>
<app appid='aplfhldgnogkgfjopdbppahookjpfpad'>
<updatecheck codebase='https://www.myextension.host.com/updateExtension/chrome_2.0.crx' version='2.0' />
</app>
</gupdate>
But when I installed the extension and click the update now, nothing happened, the server does not detect the request for the updates.xml file either.
I started chrome with
chrome.exe --enable-logging --log-level=2
but cannot find any error log about the update. Well I did see some logs but I'm not sure it's related or not. Post below too:
[5468:1956:0515/114000:ERROR:accelerated_surface_win.cc(208)] Reseting D3D device
[5468:188:0515/114003:ERROR:textfield.h(156)] NOT IMPLEMENTED
[5468:428:0515/114007:ERROR:accelerated_surface_win.cc(208)] Reseting D3D device
[4500:476:0515/114131:ERROR:ipc_channel_win.cc(132)] pipe error: 109
[5468:3560:0515/114131:ERROR:accelerated_surface_win.cc(208)] Reseting D3D device
[5468:3048:0515/114218:ERROR:accelerated_surface_win.cc(208)] Reseting D3D device
[5676:1276:0515/120110:ERROR:ipc_channel_win.cc(132)] pipe error: 109
[3596:6072:0515/120540:ERROR:ipc_channel_win.cc(132)] pipe error: 109
Is there any debug way to better debug the update operation?
Upvotes: 1
Views: 1894
Reputation: 348992
To get debugging information about the extension's updater process, start Chrome / Chromium with the following command:
chrome.exe --vmodule=extension_updater=2 --enable-logging
After starting Chrome, a log file called chrome_debug.log
will be created in your user profile directory.
Without any other information, I guess that you've either got a typo in the extension ID or in the update URL. If your extension still doesn't install after fixing this issue, check whether the crx file is served with the application/x-chrome-extension
MIME-type.
Upvotes: 3