After some recently rolled out policy updates with Chrome, we are now experiencing the unpacked extension issue when running Protractor E2E tests with Selenium Web Driver.
The error is:
Failed to load extension from:C:\Users\...\AppData\Local\Temp\scoped_dir9090_11922\internal.
Loading of unpacked extensions is disabled by the administrator.
This internal folder was unziped from internal.zip, and contains the following manifest.json:
{
"key": "MIGfMA0GCSqGSI...",
"name": "Chrome Automation Extension",
"version": "1",
"manifest_version": 2,
"description": "Exposes extension APIs for automating Chrome",
"background": {
"scripts": ["background.js"]
},
"permissions": [
"tabs", "management", "<all_urls>"
]
}
In the protractor config file we tried to disable extensions here, but it had no effect:
multiCapabilities: [
{
browserName: 'chrome',
chromeOptions: {
args: [
'--disable-extensions', '--disable-plugins', '--start-maximized'
]
}
},
]
As per comment 22 on March 31st in this Chrome bug, they introduced a new Chrome option, --useAutomationExtension. So as soon as I get Protractor working again on my box, I will try it as follows:
chromeOptions: {
args: [
'--disable-extensions', '--disable-plugins', '--start-maximized',
'--useAutomationExtension=false'
]
}
My primary question is:
Has anyone pinpointed exactly the extension name which is unpacked, and what to communicate to their IT department for whitelist purposes? Here is an old post which addresses this issue.
In addition:
- Has anyone successfully implemented the
--useAutomationExtension=falseoption in protractor.conf.js?
I will update this post as I progress throughout the day, hoping to add some clarity.