You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
ProtocolError: Waiting for selector [data-testid="intro-md-beta-logo-dark"], [data-testid="intro-md-beta-logo-light"], [data-asset-intro-image-light="true"], [data-asset-intro-image-dark="true"],[data-icon="intro-md-beta-logo-dark"], [data-icon="intro-md-beta-logo-light"] failed: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.
at <instance_members_initializer> (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Connection.js:42:14)
at new Callback (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Connection.js:46:16)
at CallbackRegistry.create (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Connection.js:86:26)
at Connection._rawSend (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Connection.js:208:26)
at CdpCDPSession.send (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/CDPSession.js:61:33)
at #evaluate (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/ExecutionContext.js:211:50)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async ExecutionContext.evaluateHandle (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/ExecutionContext.js:178:16)
at async IsolatedWorld.evaluateHandle (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/IsolatedWorld.js:124:16)
at async CdpJSHandle.evaluateHandle (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/api/JSHandle.js:166:20)
at async WaitTask.rerun (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/common/WaitTask.js:104:28)
Describe the solution you'd like.
How can I solve the timeout not being so fast and giving the error?
Describe an alternate solution.
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Is your feature request related to a problem? Please describe.
ProtocolError: Waiting for selector
[data-testid="intro-md-beta-logo-dark"], [data-testid="intro-md-beta-logo-light"], [data-asset-intro-image-light="true"], [data-asset-intro-image-dark="true"],[data-icon="intro-md-beta-logo-dark"], [data-icon="intro-md-beta-logo-light"]
failed: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.at <instance_members_initializer> (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Connection.js:42:14)
at new Callback (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Connection.js:46:16)
at CallbackRegistry.create (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Connection.js:86:26)
at Connection._rawSend (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Connection.js:208:26)
at CdpCDPSession.send (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/CDPSession.js:61:33)
at #evaluate (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/ExecutionContext.js:211:50)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async ExecutionContext.evaluateHandle (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/ExecutionContext.js:178:16)
at async IsolatedWorld.evaluateHandle (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/IsolatedWorld.js:124:16)
at async CdpJSHandle.evaluateHandle (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/api/JSHandle.js:166:20)
at async WaitTask.rerun (/home/webwhatsapp/node_modules/puppeteer-core/lib/cjs/puppeteer/common/WaitTask.js:104:28)
Describe the solution you'd like.
How can I solve the timeout not being so fast and giving the error?
Describe an alternate solution.
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: