Protractor Failed to run after new Enterprise Policies push to the computer "loading of unpacked extensions is disabled by the administrator"

[acostaf]

I got this this nice error with the new policies "loading of unpacked extensions is disabled by the administrator"

[juliemr]

This looks like a problem specific to your machine/network. At what point does the error occur? What browser? Are you indeed loading an extension in your setup?

[acostaf]

HI @juliemr

I am using Protactor 1.4, Angular 1.3.4, chromedriver 2.12.0 and chrome 41, now the new policy blocked extensions and I get the error as soon as I run protractor

C:\Users\user\trunk\net\project.Tests>grunt uiTest
Running "iis-killer" task

Running "iisexpress:server" (iisexpress) task

Started IIS Express.

Running "concurrent:uiTest" (concurrent) task
Successfully registered URL "http://localhost:1791/" for site "Development Web Site" application "/"
Registration completed
Warning: Running "protractor:smokeTest" (protractor) task
Starting selenium standalone server...
Selenium standalone server started at http://30.192.10.120:55945/wd/hub
[launcher] Error: UnknownError: chrome not reachable
(Driver info: chromedriver=2.12.301325 (962dea43ddd90e7e4224a03fa3c36a421281abb7),platform=Windows NT 6.1 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 60.89 seconds
Build info: version: '2.43.1', revision: '5163bce', time: '2014-09-10 16:27:33'
System info: host: 'F2C44FD141168', ip: '30.192.10.120', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_65'
Driver info: org.openqa.selenium.chrome.ChromeDriver
at new bot.Error (C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\selenium-webdriver\lib\atoms\error.js:113:18)
at Object.bot.response.checkResponse (C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\selenium-webdriver\lib\atoms\response.js:106:9)
at C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:152:24
at C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\selenium-webdriver\lib\goog\base.js:1582:15
at webdriver.promise.ControlFlow.runInNewFrame_ (C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:1654:20)
at notify (C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:465:12)
at notifyAll (C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:442:7)
at resolve (C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:420:7)
at fulfill (C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:535:5)
at C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\selenium-webdriver\lib\goog\base.js:1582:15
==== async task ====
WebDriver.createSession()
at Function.webdriver.WebDriver.acquireSession_ (C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:149:22)
at Function.webdriver.WebDriver.createSession (C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:123:30)
at Builder.build (C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\selenium-webdriver\builder.js:294:22)
at LocalDriverProvider.getDriver (C:\Users\user\trunk\net\project.Tests\node_modules\protractor\lib\driverProviders\local.js:121:9)
at C:\Users\user\trunk\net\project.Tests\node_modules\protractor\lib\runner.js:222:41
at _fulfilled (C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\q\q.js:797:54)
at self.promiseDispatch.done (C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\q\q.js:826:30)
at Promise.promise.promiseDispatch (C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\q\q.js:759:13)
at C:\Users\user\trunk\net\project.Tests\node_modules\protractor\node_modules\q\q.js:573:44

Fatal error: protractor exited with code: 100 Use --force to continue.

Aborted due to warnings.

[juliemr]

Are you loading an extension in your setup? What does your capabilities object look like?

I'm afraid that this is an issue with your specific machine and not something that Protractor generally can help with.

[juliemr]

Haven't heard anything from a bit - this looks like it's not a general issue so I'm closing. Please open a new issue if you believe that there is a bug with protractor. Thanks!

[zsong]

seleniumAddress: 'http://localhost:4444/wd/hub',
capabilities: {
    browserName: 'chrome',
    chromeOptions: {
        args: ['disable-extensions', 'disable-plugins']
    }
},

I got same exact error. Here is my config.

[VishwaKumar]

I got the same issue today "Error loading Extension" and this is my config

exports.config = {
    directConnect: true,

    // Capabilities to be passed to the webdriver instance.
    capabilities: {
        'browserName': 'chrome'
    },

    // Framework to use. Jasmine is recommended.
    framework: 'jasmine',

    // Spec patterns are relative to the current working directory when
    // protractor is called.
    specs: [
        '../ui.apps/src/test/e2e/control-flow-delay.js',

        '../app/src/test/e2e/mypage.test.js',
    ],

    // Options to be passed to Jasmine.
    jasmineNodeOpts: {
        defaultTimeoutInterval: 1000000
    },

    allScriptsTimeout: 120000,

    onPrepare: function() {
        setTimeout(function() {
            browser.driver.executeScript(function() {
                return {
                    width: window.screen.availWidth,
                    height: window.screen.availHeight
                };
            }).then(function(result) {
                browser.driver.manage().window().setSize(result.width, result.height);
            });
        });
    },
};

When i ran protractor, the error was coming and chrome browser would open and be idle with "No Secure data" in the address bar.

But strangely i found out that , once i commented the lines of code in the onPrepare function, the error "Error loading Extension" still came but the chrome browser ran normally and all my test cases got executed successfully. I am new to node and protractor so i couldn't debug why commenting those lines of code ran my test-cases normally.

Hope this helps anyone facing the same issue.