Skip to content

Error after original connection #16

@mwelby

Description

@mwelby

Hi - the script worked for 100 connections and stated too many requests and now it is throwing an error as below:

Connecting to the LinkedIn server..(node:7632) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'status' of undefined
at C:\Users\MYPC\AppData\Roaming\npm\node_modules\linkedin-auto-connect\lib\scraper.js:25:22
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:7632) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:7632) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions