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 am using the WPPConnect API to initiate a WhatsApp session and expect to receive a QR code for the connection process. However, the /start-session endpoint returns a status of "INITIALIZING" without providing a QR code. Subsequent status checks also reflect the same "INITIALIZING" status with no QR code. This issue prevents me from completing the WhatsApp connection process.
Generate a token using this endpoint - /generate-token
Start a session by providing details - /start-session
i have used this payload
{
"webhook": "",
"waitQrCode": true
}
response - {
"status": "INITIALIZING",
"qrcode": null,
"version": "2.4.2",
"session": "------there will be a session id returned from this api---------"
}
than checked the status session multiple times, even on some intervals using this endpoint - /status-session
response - {
"status": "INITIALIZING",
"qrcode": null,
"version": "2.4.2"
}
The text was updated successfully, but these errors were encountered:
Description
I am using the WPPConnect API to initiate a WhatsApp session and expect to receive a QR code for the connection process. However, the /start-session endpoint returns a status of "INITIALIZING" without providing a QR code. Subsequent status checks also reflect the same "INITIALIZING" status with no QR code. This issue prevents me from completing the WhatsApp connection process.
Environment
WPPConnect version(s): v1.34.1
WA-JS version(s): 3.10.1
Browser: Chrome
OS: Ubuntu 22.04
Node version: 20.13.1
WhatsApp version: 2.3000.1015690181
Steps to Reproduce
i have used this payload
{
"webhook": "",
"waitQrCode": true
}
response - {
"status": "INITIALIZING",
"qrcode": null,
"version": "2.4.2",
"session": "------there will be a session id returned from this api---------"
}
response - {
"status": "INITIALIZING",
"qrcode": null,
"version": "2.4.2"
}
The text was updated successfully, but these errors were encountered: