returning to angular after non-angular login doesn't work

[thatbudakguy]

I have a spec almost identical to the nonAngularLoginSpec - loading a non-angular page basically the same as nonAngularLoginPage, entering credentials, and then returning to Angular (something like friendsPage). When I test for the equivalent of friendsPage.at(); I always get:

  - Expected false to be truthy.

Presumably this is because browser.ignoreSynchronization = true; is still enabled, but even if I manually add browser.ignoreSynchronization = false; and/or browser.waitForAngular(); before testing friendsPage.at();, protractor still won't wait for angular to load. Any ideas?

[qualityshepherd]

This isn't a bug, and should be asked via Stack Overflow.

That said, I was curious, so I tried adding an angular test (from friendSpec) at the end of the nonAngularLoginSpec, and it did indeed fail. But if I put in a friendsPage.goto() (note: used to be to()) in the spec, it worked like a charm.

Not sure if adding browser.ignoreSynchronization = true; to non-angular pages is a convention, but it seems like it could be :)