title: Protractor test does not finish, seems to loop until the jasmine timeout error hits
body: <p>I feel pretty dumb to not be able to get the most basic protractor test to work. Given protractor 5.4.1 i have a spec.js</p>
  
  <pre><code>describe('my example tests', () =&gt; {
    const EC = protractor.ExpectedConditions;
      it('tests google', async () =&gt; {
        await browser.waitForAngularEnabled(false);
        await browser.get("https://google.com");
        await browser.wait(EC.visibilityOf($('input')));
        await element(by.css("input")).click();});});
  </code></pre>
  
  <p>and a conf of </p>
  
  <pre><code>exports.config = {
  
    directConnect: true,
    specs: ['tests/**/*.js'],
    capabilities: {
      browserName: 'chrome',
    },
  
    SELENIUM_PROMISE_MANAGER: false,
  
    jasmineNodeOpts: {
      defaultTimeoutInterval: 40000
    }
  };
  </code></pre>
  
  <p>when running <code>protractor conf.js</code> the browser opens, goes to the page and then nothing happens until the 40s jasmine timeout hits. What I get are ~25 warnings per second<br>
  <code>W/element - more than one element found for locator By(css selector, input) - the first result will be used</code><br>
  as if some command is running in an endless loop until I get an error <code>Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.</code> which does not tell me much and is hard to google.</p>
  
  <p>Has anyone experienced this issue?</p>