Timeout while waiting to synchronize

Hi! I just picked up mobile testing here and having a go at our site with protractor (as we dearly miss decent automation on mobile), but couldn’t get it to even load up properly (protractor, that is). The whole testcase is:

describe('ms2 homepage', function() {
  it('should not redirect', function() {
    browser.get('https://sports.m.bwin.es/en/sports');
    expect(browser.getCurrentUrl()).toContain('sports.m.bwin.es/en/sports');
    // yes, thats pretty redundant, but its good enough for triggering the issue
  });
});

which results in a timeout with this output:

D:\svn\MS2\FuncTest>protractor conf.js
Using the selenium server at http://localhost:4444/wd/hub
F

Failures:

  1) ms2 homepage should not redirect
   Message:
     Error: Timed out waiting for Protractor to synchronize with the page after 11 seconds
   Stacktrace:
     Error: Timed out waiting for Protractor to synchronize with the page after 11 seconds
    at Error (<anonymous>)
    at [...]\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:1318:15
    at [...]\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:1467:7
    at [...]\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\goog\base.js:1178:15
    at webdriver.promise.ControlFlow.runInNewFrame_ ([...]\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\
webdriver\promise.js:1445:20)
    at notify ([...]\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:328:12)
    at notifyAll ([...]\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:297:7)
    at handleRejection ([...]\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:419:7)
    at reject [as errback] ([...]\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:429:
7)
    at reject ([...]\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:1631:5)
==== async task ====
WebDriver.executeScript()
    at webdriver.WebDriver.schedule ([...]\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdri
ver.js:267:15)
    at webdriver.WebDriver.executeAsyncScript ([...]\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdri
ver\webdriver.js:507:15)
    at Protractor.waitForAngular ([...]\npm\node_modules\protractor\lib\protractor.js:407:22)
    at to.(anonymous function) [as getCurrentUrl] ([...]\npm\node_modules\protractor\lib\protractor.js:41:7)
    at null.<anonymous> (D:\svn\MS2\FuncTest\example_spec.js:5:20)
    at [...]\npm\node_modules\protractor\jasminewd\index.js:54:12
    at webdriver.promise.ControlFlow.runInNewFrame_ ([...]\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\
webdriver\promise.js:1445:20)
    at webdriver.promise.ControlFlow.runEventLoop_ ([...]\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\w
ebdriver\promise.js:1310:8)
    at wrapper [as _onTimeout] (timers.js:252:14)
==== async task ====
    at null.<anonymous> ([...]\npm\node_modules\protractor\jasminewd\index.js:53:12)
    at null.<anonymous> ([...]\npm\node_modules\protractor\node_modules\minijasminenode\lib\async-callback.js:45:37)
    at jasmine.Block.execute ([...]\npm\node_modules\protractor\node_modules\minijasminenode\lib\jasmine-1.3.1.js:1168:17)
    at jasmine.Queue.next_ ([...]\npm\node_modules\protractor\node_modules\minijasminenode\lib\jasmine-1.3.1.js:2200:31)
    at null._onTimeout ([...]\npm\node_modules\protractor\node_modules\minijasminenode\lib\jasmine-1.3.1.js:2190:18)
    at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

Finished in 12.181 seconds
1 test, 1 assertion, 1 failure

I also already tried increasing the timeout to bigger values but with no success.

[thilinadinith]

@juliemr - protractor in angular is not working with changing pages with synchronization

Error: Timed out waiting for Protractor to synchronize with the page after 11 seconds

option is making the ignore.Synchronization = true ; But then again its getting problem that angular is not define as its not synchronized

@juliemr - DO NOT TELL LOOK YOUR DOCUMENTATION AS THERE IS NOTHING on it and people get really helpless due to your poor documentation !!

[FrankyBoy]

Jop, we had a bunch of $timeouts in a loop (slideshow) which for obvious reasons failed to ever be considered “stable”. Right now we (actually another department) have only one “problem” with the sync which is that they have auto-hiding notification messages (which use $timeout) which then obviously block until they disappear … and their devs are like “We’ll never use $interval with 1 repetition for that” so tough luck 😉

@thilinadinith srsly, learn some manners. also maybe provide some code to reproduce the issue, because right now you are just flaming around. If there really is an issue in protractor I can say from the past that it usually got treated with the appropriate seriousness.