-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Synthetic Recorder not working in MacOS 15.0 Sequoia #533
Comments
Identical behaviour on MacOS Sequoia 15.1 and Recorder Version 1.3.0 (1.3.0.2):
|
I also got this shortly after upgrading to the latest version (15.1.1):
|
I am facing the same issue after Mac upgraded to 15.1.1 |
Hi Team, I'm getting same issue post upgraded my Mac device to 15.1.1. It will be really help helpful, if we get any solution/advise. Thank you. |
These are the logs I see when getting the error, (MacOS version 15.1.1), fresh install of: https://github.com/elastic/synthetics-recorder/releases/download/v1.3.0/synthetics-recorder-1.3.0-mac-arm64.dmg. I even deleted everything in
|
Anyone have any updates on this? I am seeing the same error. |
Bug summary
Hi,
The Elastic Synthetic recorder is not working on MacOS Sequoia v15.0 , when we hit the Start recording getting below error.
Unhandled Promise Rejection Error: Page closed at CRSession.<anonymous> (/private/var/folders/_4/pmb9slfs3lxdrs8q6wf1670w0000gr/T/AppTranslocation/A352FFA7-37A7-4D41-A63F-93C95EE1C5A4/d/Elastic Synthetics Recorder.app/Contents/Resources/app.asar/node_modules/playwright-core/lib/server/chromium/crPage.js:377:54) at Object.onceWrapper (node:events:641:28) at CRSession.emit (node:events:539:35) at /private/var/folders/_4/pmb9slfs3lxdrs8q6wf1670w0000gr/T/AppTranslocation/A352FFA7-37A7-4D41-A63F-93C95EE1C5A4/d/Elastic Synthetics Recorder.app/Contents/Resources/app.asar/node_modules/playwright-core/lib/server/chromium/crConnection.js:211:39
Thanks,
Recorder Version
1.3.0
Steps to reproduce
Issue:
Expected behavior
Chromium browser should open, instead error thrown
Additional information
No response
The text was updated successfully, but these errors were encountered: