npm run protractor fail

[clp334264003]

H:\QiaoMuArborWorkSpace\angular-phonecat>npm run protractor

> angular-phonecat@0.0.0 preprotractor H:\QiaoMuArborWorkSpace\angular-phonecat
> npm run update-webdriver


> angular-phonecat@0.0.0 preupdate-webdriver H:\QiaoMuArborWorkSpace\angular-pho
necat
> npm install


> angular-phonecat@0.0.0 postinstall H:\QiaoMuArborWorkSpace\angular-phonecat
> bower install


> angular-phonecat@0.0.0 update-webdriver H:\QiaoMuArborWorkSpace\angular-phonec
at
> webdriver-manager update

selenium standalone is up to date.
chromedriver is up to date.

> angular-phonecat@0.0.0 protractor H:\QiaoMuArborWorkSpace\angular-phonecat
> protractor test/protractor-conf.js

[19:31:37] I/local - Starting selenium standalone server...
[19:31:38] I/launcher - Running 1 instances of WebDriver
[19:31:39] I/local - Selenium standalone server started at http://192.168.31.138
:56068/wd/hub
Started
.F

Failures:
1) PhoneCat App Phone list view should display the current filter value within a
n element with id "status"
  Message:
    Failed: element(...).text is not a function
  Stack:
    TypeError: element(...).text is not a function
        at Object.<anonymous> (H:\QiaoMuArborWorkSpace\angular-phonecat\test\e2e
\scenarios.js:31:39)
        at H:\QiaoMuArborWorkSpace\angular-phonecat\node_modules\protractor\node
_modules\jasminewd2\index.js:96:23
        at new Promise (H:\QiaoMuArborWorkSpace\angular-phonecat\node_modules\pr
otractor\node_modules\selenium-webdriver\lib\promise.js:1043:7)
        at controlFlowExecute (H:\QiaoMuArborWorkSpace\angular-phonecat\node_mod
ules\protractor\node_modules\jasminewd2\index.js:82:18)
        at TaskQueue.execute_ (H:\QiaoMuArborWorkSpace\angular-phonecat\node_mod
ules\protractor\node_modules\selenium-webdriver\lib\promise.js:2790:14)
        at TaskQueue.executeNext_ (H:\QiaoMuArborWorkSpace\angular-phonecat\node
_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2773:21)
        at H:\QiaoMuArborWorkSpace\angular-phonecat\node_modules\protractor\node
_modules\selenium-webdriver\lib\promise.js:2697:25
        at H:\QiaoMuArborWorkSpace\angular-phonecat\node_modules\protractor\node
_modules\selenium-webdriver\lib\promise.js:639:7
        at process._tickCallback (node.js:369:9)
    From: Task: Run it("should display the current filter value within an elemen
t with id "status"") in control flow
        at Object.<anonymous> (H:\QiaoMuArborWorkSpace\angular-phonecat\node_mod
ules\protractor\node_modules\jasminewd2\index.js:81:14)
        at H:\QiaoMuArborWorkSpace\angular-phonecat\node_modules\protractor\node
_modules\jasminewd2\index.js:18:5
        at Promise.invokeCallback_ (H:\QiaoMuArborWorkSpace\angular-phonecat\nod
e_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:1329:14)
        at TaskQueue.execute_ (H:\QiaoMuArborWorkSpace\angular-phonecat\node_mod
ules\protractor\node_modules\selenium-webdriver\lib\promise.js:2790:14)
        at TaskQueue.executeNext_ (H:\QiaoMuArborWorkSpace\angular-phonecat\node
_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2773:21)
        at H:\QiaoMuArborWorkSpace\angular-phonecat\node_modules\protractor\node
_modules\selenium-webdriver\lib\promise.js:2652:27
    From asynchronous test:
    Error
        at Suite.<anonymous> (H:\QiaoMuArborWorkSpace\angular-phonecat\test\e2e\
scenarios.js:29:5)
        at Suite.<anonymous> (H:\QiaoMuArborWorkSpace\angular-phonecat\test\e2e\
scenarios.js:7:3)
        at Object.<anonymous> (H:\QiaoMuArborWorkSpace\angular-phonecat\test\e2e
\scenarios.js:5:1)

2 specs, 1 failure
Finished in 1.152 seconds
[19:31:43] I/local - Shutting down selenium standalone server.
[19:31:43] I/launcher - 0 instance(s) of WebDriver still running
[19:31:43] I/launcher - chrome #01 failed 1 test(s)
[19:31:43] I/launcher - overall: 1 failed spec(s)
[19:31:43] E/launcher - Process exited with error code 1

[gkalpak]

The tutorial has been updated with #326. All dependencies and tools have been updated (along with many tests) and this is hopefully not an issue any more.
If anyone is still having problems, please open a new issue.