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
I have checked and am using the latest version of the library.
What type of session are you experiencing this issue on?
Multi-device and I have set multiDevice to true in my config OR am using the --multi-device flag
What type of host account are you experiencing this issue on?
Business account
Mode
EASY API/CLI
Current Behavior
createGroup created groups with easyAPI
default approval mode: Require admin approval.
-- URL: http://xxxx:8085/setGroupApprovalMode
-- Data: {"args":{"groupId":"xxxxx@g.us","requireApproval":false}}
Set group approval mode response: {"success":true}
BUT
This does NOT change the admin approval mode. Instead it changes 'EDIT GROUP SETTINGS' permission (retureApproval=True sets editSettings to False and vice versa)
Expected Behavior
GroupApprovalMode permission should be set correctly
middleware -> error ProtocolError: Protocol error (Runtime.callFunctionOn): Promise was collected
at Callback (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:61:35)
at CallbackRegistry.create (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:106:26)
at Connection._rawSend (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:216:26)
at CDPSessionImpl.send (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:425:78)
at ExecutionContext._ExecutionContext_evaluate (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:240:46)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async ExecutionContext.evaluate (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:146:16)
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Are you using the latest version of the library?
What type of session are you experiencing this issue on?
Multi-device and I have set multiDevice to true in my config OR am using the --multi-device flag
What type of host account are you experiencing this issue on?
Business account
Mode
EASY API/CLI
Current Behavior
createGroup created groups with easyAPI
default approval mode: Require admin approval.
-- URL: http://xxxx:8085/setGroupApprovalMode
-- Data: {"args":{"groupId":"xxxxx@g.us","requireApproval":false}}
Set group approval mode response: {"success":true}
BUT
This does NOT change the admin approval mode. Instead it changes 'EDIT GROUP SETTINGS' permission (retureApproval=True sets editSettings to False and vice versa)
Expected Behavior
GroupApprovalMode permission should be set correctly
Steps To Reproduce
-- Data: {"args":{"groupId":"xxxxxx@g.us","requireApproval":true}}
-- Response: {"success":true}
but as described above, a different permission flag is toggled
create() code OR full CLI command + CONFIG
No response
DEBUG INFO
Environment
Screenshots/Logs
Not sure if this console error is related
middleware -> error ProtocolError: Protocol error (Runtime.callFunctionOn): Promise was collected
at Callback (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:61:35)
at CallbackRegistry.create (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:106:26)
at Connection._rawSend (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:216:26)
at CDPSessionImpl.send (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:425:78)
at ExecutionContext._ExecutionContext_evaluate (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:240:46)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async ExecutionContext.evaluate (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:146:16)
Anything else?
No response
The text was updated successfully, but these errors were encountered: