Protractor hangs completely when trying to get any element property after logging in (idk if it's related to logging in or related just to switching pages).

```
it("Should get location of main container", async function() {
    await LoginPage.validLogin();
    // Works and logs in the dashboard
    await browser.sleep(3000);
    // Get the main container by class name
    const container = await element(by.css(".main-container"));
    // Logs properly the element functions (as expected)
    console.log(container);
    console.log(await container.getLocation()); // Hangs here
});

```

In this case, I'm trying to get the location of the main container element on the page. The first console.log fires and shows properly, while the second hangs completely, so I get the script timeout. Increasing the timeout time doesn't help at all...

I found online that misusing $timeout in AngularJS instead of using $interval may lead to this strange behaviour, but I really can't skim through the entire (very big!) project's codebase to change everything hoping that it just works, not to talk about the external libraries using $timeout.

I have SELENIUM\_PROMISE\_MANAGER = false; in my Protractor config so I disabled the built-in Control Flow in order to manually manage the promises using async/await, but even if I use the built-in Control Flow without using async/await I get the very same behaviour and error.
I'm using Jasmine as testing framework.

Maybe I'm missing something? Any help would be much appreciated, thanks!