-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
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
[BUG] sendPresenceUpdate() fails when connecting via QR #893
Labels
bug
Something isn't working
Comments
oscarguindzberg
added a commit
to bluepepperok/Baileys
that referenced
this issue
Jun 25, 2024
oscarguindzberg
added a commit
to oscarguindzberg/Baileys
that referenced
this issue
Jun 25, 2024
This is a temporary workaround oscarguindzberg@da32b39 |
it's not a bug |
oscarguindzberg
added a commit
to bluepepperok/Baileys
that referenced
this issue
Aug 26, 2024
oscarguindzberg
added a commit
to bluepepperok/Baileys
that referenced
this issue
Aug 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
chat.ts
sendPresenceUpdate()
fails when connecting via QRBaileys/src/Socket/chats.ts
Line 544 in 76d2a9d
This is printed on the logs:
{"level":40,"time":"2024-06....","pid":37...,"hostname":"myHost","msg":"no name present, ignoring presence update request..."}
The cause is
authState.creds.me.name
was not set yet by the timesendPresenceUpdate()
is executed.This is a problem when using
markOnlineOnConnect: false
because:To Reproduce
Steps to reproduce the behavior:
example.ts
to usemarkOnlineOnConnect: false
example.ts
these lines:// await sock!.readMessages([msg.key])
// await sendMessageWTyping({ text: 'Hello there!' }, msg.key.remoteJid!)
{"level":40,"time":"2024-06....","pid":37...,"hostname":"myHost","msg":"no name present, ignoring presence update request..."}
Expected behavior
Environment (please complete the following information):
connectOptions
look like? : The ones in the example plusmarkOnlineOnConnect: false
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: