[🐛 Bug]: browser.executeAsync(script, arguments) returns an undefined. #13376
Description
Have you read the Contributing Guidelines on issues?
- I have read the Contributing Guidelines on issues.
WebdriverIO Version
9.0.0
Node.js Version
v22.6.0
Mode
WDIO Testrunner
Which capabilities are you using?
capabilities: [{ browserName: 'firefox' }]What happened?
The browser.executeAsync(script, arguments) function returns an undefined type instead of what is passed in done callback.
What is your expected behavior?
The browser.executeAsync(script, arguments) function returns what is passed to the done callback.
How to reproduce the bug.
$ mkdir wdio-mre; cd wdio-mre
$ curl https://pastebin.com/raw/dEU6NW9M > mre-setup.js
$ node mre-setup.js
$ npx wdio run ./wdio.conf.jsRelevant log output
[firefox 129.0.1 linux #0-0] executeAsync performs well
[firefox 129.0.1 linux #0-0] ✖ should execute async JavaScript on the page
[firefox 129.0.1 linux #0-0]
[firefox 129.0.1 linux #0-0] 1 failing (586ms)
[firefox 129.0.1 linux #0-0]
[firefox 129.0.1 linux #0-0] 1) executeAsync performs well should execute async JavaScript on the page
[firefox 129.0.1 linux #0-0] expect(received).toEqual(expected) // deep equality
Expected: 10
Received: undefined
[firefox 129.0.1 linux #0-0] Error: expect(received).toEqual(expected) // deep equality
[firefox 129.0.1 linux #0-0]
[firefox 129.0.1 linux #0-0] Expected: 10
[firefox 129.0.1 linux #0-0] Received: undefined
[firefox 129.0.1 linux #0-0] at Context.<anonymous> (file:///home/greenowl/Downloads/wdio-mre/main.test.js:15:20)Code of Conduct
- I agree to follow this project's Code of Conduct
Is there an existing issue for this?
- I have searched the existing issues