We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am encountering a WebSocket error when attempting to execute the following command: client.GetProfilePictureInfo(clientJID, params).
client.GetProfilePictureInfo(clientJID, params)
The error occurs consistently, and I receive the following message in the logs:
[WhatsMeow/Socket ERROR] Error reading from websocket: websocket: close 1006 (abnormal closure): unexpected EOF
Steps to Reproduce:
Expected Behavior:
The command should successfully fetch the profile picture information without causing a WebSocket closure.
Actual Behavior:
The WebSocket unexpectedly closes with error code 1006 (abnormal closure)
Additional Information:
Please let me know if additional logs or debug information are required.
The text was updated successfully, but these errors were encountered:
The same happens with the client.Store.Contacts.GetAllContacts()
client.Store.Contacts.GetAllContacts()
Sorry, something went wrong.
Same problem
same here
No branches or pull requests
I am encountering a WebSocket error when attempting to execute the following command:
client.GetProfilePictureInfo(clientJID, params)
.The error occurs consistently, and I receive the following message in the logs:
Steps to Reproduce:
client.GetProfilePictureInfo(clientJID, params)
with valid parameters.Expected Behavior:
The command should successfully fetch the profile picture information without causing a WebSocket closure.
Actual Behavior:
The WebSocket unexpectedly closes with error code 1006 (abnormal closure)
Additional Information:
Please let me know if additional logs or debug information are required.
The text was updated successfully, but these errors were encountered: