-
Notifications
You must be signed in to change notification settings - Fork 575
Error on end, Unhandled Promise #187
Comments
Same issue to me |
I have same issue. |
Same issue, but in my case I am playing one video asset on browser. It looks like node process is getting terminated but not chrome browser with |
same issue with me. |
Seeing it here too |
Curious if any of the above cases trigger a |
Seems to occur even without doing anything for me: const { Chromeless } = require('chromeless')
async function run() {
const chromeless = new Chromeless()
await chromeless.end()
}
run().catch(console.error.bind(console)) Node v8.1.3 |
By making sure we're passing the right target to newly launched chrome instance and later into the CDP.Close(...) call Closes schickling#187
I'm still experiencing this issue in version 1.2 using the same codeblock that @mx781 had posted. Any updates? |
A new version hasn't been cut yet with the fix. |
Still having the problem, with the given example - const { Chromeless } = require('chromeless')
async function run() {
const chromeless = new Chromeless()
const screenshot = await chromeless
.goto('https://www.google.com')
.type('chromeless', 'input[name="q"]')
.press(13)
.wait('#resultStats')
.screenshot()
console.log(screenshot) // prints local file path or S3 url
await chromeless.end()
}
run().catch(console.error.bind(console)) The error -
|
Idem, same error with the given example.
|
@adieuadieu Why don't you just release new version? |
I'm sorry for the delay. Just published v1.3.0 to NPM. Please do let us know if it resolves these issues! |
It's working perfectly 👍 |
Itou. Nickel 👍 |
By making sure we're passing the right target to newly launched chrome instance and later into the CDP.Close(...) call Closes schickling#187
I'm using v1.2.0 to have chromless log into spotify and get the user auth token to manage a playlist (they have to be associated to a user not an application).
After
chromeless.end
I get an unhandeled promise rejection. I do briefly see chrome asking to save the password? Maybe not related.the code requires working username and password
Edit: To be clear. Even with a catch on both awaits the error is not caught and throws a UnhandledPromiseRejectionWarning.
The text was updated successfully, but these errors were encountered: