sessions not working properly #1894
Comments
|
Hello, everything is working fine. Try posting your complete code (with the call that reuses the session) and formatted for better readability. For manual testing, use the pure code by directly calling the session and manually specifying the session name for your tests. This way, you can pinpoint where the issue in your code might be. |
|
Hello, I'm also having the same issues as @joelvasiliev. When I create a new client with a new session: this.client = await create({
session: this.session,
deviceName: `${name} WhatsApp Client`,
statusFind: statusCallback,
catchQR: qrCallback,
waitForLogin: true,
debug: true,
autoClose: 60 * 2 * 1000,
folderNameToken: `clients/whatsapp`,
onLoadingScreen: loadingCallback,
logQR: true,
});I get the following output on the console The session id is |
|
device not connecting |
|
Session Unpaired |
|
error: Unhandled Rejection: ProtocolError: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed. |
|
debug: Emitting onInterfaceChange event (1 registered) |
|
debug: Emitting onInterfaceChange event (1 registered) |
|
Same here! |
|
Hello, I'm having the same issue here that is will be only SYNCING (SYNCING) and it just hang there. |
I had the same error, I fixed it by adding the folderNameToken parameter. const wppClient = await create({
session: props.session,
deviceName: props.deviceName,
poweredBy: props.poweredBy || "WPPConnect-Server",
folderNameToken: `./tokens/${props.session}`,
headless: true,
useChrome: true,
debug: false,
logQR: false,
browserArgs: [],
onLoadingScreen: (percent, message) => { },
catchQR: (base64Qr, asciiQR, attempt, urlCode) => { },
statusFind: (statusFind) => { },
}).then(async (client) => { }); |
Description
Hi, I'm working with multiple sessions, and I do have this code:
app.post('/whatsapp/session', function (req, res) { const id = randomUUID(); wppconnect .create({ session: id, catchQR: (base64Qr) => { sessions.push({ id, client: null, qr: base64Qr.split(',')[1], error: false, }); }, headless: true, // Headless chrome useChrome: false, // If false will use Chromium instance debug: true, // Opens a debug session logQR: true, // Logs QR automatically in terminal updatesLog: true, // Logs info updates automatically in terminal autoClose: 30000, // Automatically closes the wppconnect only when scanning the QR code (default 60 seconds, if you want to turn it off, assign 0 or false) tokenStore: 'file', // Define how work with tokens, that can be a custom interface })When I make a POST request with Postman, it works fine the first time, but on the second one, it reuses the previous token folder.
Evidence:"
"In the second image, the ID in the session is 'f0879c68-0d88-4d20-a301-4430b7056846,' and it is using the 'tokens' folder in the path 'tokens\9e56bf2c-6fc5-44b6-a7fb-b62e48daf720,'' which would be the ID of the first request made."
Environment
The text was updated successfully, but these errors were encountered: