Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Bug: Throwing TypeError (Version 1.2.6)

See original GitHub issue

Working Version: 1.2.5
Broken Version: 1.2.6
NPM Repo: https://www.npmjs.com/package/protractor-beautiful-reporter

This morning I went to run Protractor and got the below error. I noticed that the version of this module was updated last night. This bug must have been introduced.

env

OS: Windows 7 64bit Chrome version: Version 70.0.3538.77 (Official Build) (64-bit)

Error:

[15:30:48] E/launcher - Error: TypeError: Cannot set property 'searchSettings' of undefined
    at new ScreenshotReporter (C:\Users\RonanC\development\myApp\node_modules\protractor-beautiful-reporter\index.js:4672:47)
    at onPrepare (C:\Users\RonanC\development\myApp\e2e\protractor.conf.js:82:38)
    at q_1.Promise (C:\Users\RonanC\development\myApp\node_modules\protractor\built\util.js:46:49)
    at Function.promise (C:\Users\RonanC\development\myApp\node_modules\q\q.js:682:9)
    at Object.runFilenameOrFn_ (C:\Users\RonanC\development\myApp\node_modules\protractor\built\util.js:38:16)
    at plugins_.onPrepare.then (C:\Users\RonanC\development\myApp\node_modules\protractor\built\runner.js:98:27)
    at _fulfilled (C:\Users\RonanC\development\myApp\node_modules\q\q.js:834:54)
    at C:\Users\RonanC\development\myApp\node_modules\q\q.js:863:30
    at Promise.promise.promiseDispatch (C:\Users\RonanC\development\myApp\node_modules\q\q.js:796:13)
    at C:\Users\RonanC\development\myApp\node_modules\q\q.js:556:49
[15:30:48] E/launcher - Process exited with error code 100
An unexpected error occurred: undefined

Issue Analytics

State:
Created 5 years ago
Comments:14 (1 by maintainers)

Top GitHub Comments

2reactions

miller45commented, Nov 12, 2018

@RonanC Thank you for the full callstack…helped me to isolate the issue very fast…

1reaction

miller45commented, Nov 12, 2018

@RonanC @matukaz is fixed now in version 1.2.7

Top Results From Across the Web

Bug listing with status RESOLVED with resolution FIXED as at ...

doesn't seem to catch -r* version suffixes" status:RESOLVED resolution:FIXED ... Bug:866 - "xmms 1.2.6-r2 (update to -r1)" status:RESOLVED resolution:FIXED ...

Runtime TypeError ("Cannot read property 'call' of undefined ...

I got version 2.5.0 of webpack and put it manually in the node_modules folder of angular cli but the issue still persists. When...

npm ERR! Invalid version: "1" - Stack Overflow

When doing "node app" on my local machine, everything works. But when I deploy my project to the Google App Engine, the instance...

Release and Version History — pipenv 2022.12.20.dev0 ...

Fixed a bug which sometimes caused pipenv to throw a TypeError or to run into encoding issues when writing a Lockfile on python...

1.2 Changelog — SQLAlchemy 2.0 Documentation

1.2.6. orm; engine; sql; postgresql; mssql; oracle; misc. 1.2.5 ... is exercised in a mock style for all three casing conventions on all...