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?
Personal account (normal)
Mode
EASY API/CLI
Current Behavior
Whenever using await Client.getAllUnreadMessages();, it returns this error:
Error [TypeError]: _0x30d707("NyC" + "SU") is not a function
window.. (pptr:evaluate;E%3A%5CAmecaCore%5Cnode_modules%5C%40open-wa%5Cwa-automate%5Cdist%5Ccontrollers%5Cpatch_manager.js%3A127%3A50:1:270204)
async Promise.all (index 1)
at window.. (evaluate at E:\AmecaCore\node_modules@open-wa\wa-automate\dist\controllers\patch_manager.js:127:50, :0:270203)
at #evaluate (E:\AmecaCore\node_modules\puppeteer-core\lib\cjs\puppeteer\cdp\ExecutionContext.js:222:56)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async ExecutionContext.evaluate (E:\AmecaCore\node_modules\puppeteer-core\lib\cjs\puppeteer\cdp\ExecutionContext.js:117:16)
at async IsolatedWorld.evaluate (E:\AmecaCore\node_modules\puppeteer-core\lib\cjs\puppeteer\cdp\IsolatedWorld.js:124:16)
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?
Personal account (normal)
Mode
EASY API/CLI
Current Behavior
Whenever using
await Client.getAllUnreadMessages();
, it returns this error:Code:
Expected Behavior
Fetch the unread messages.
Steps To Reproduce
Use await Client.getAllUnreadMessages();
create() code OR full CLI command + CONFIG
DEBUG INFO
Environment
Screenshots/Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: