Skip to content

fix: improve remote JID handling in SherpaProvider to ensure correct … #1178

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.

Sign up for GitHub

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

Merged
leifermendez merged 1 commit into from
Nov 27, 2025
Merged

fix: improve remote JID handling in SherpaProvider to ensure correct … #1178

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion packages/provider-sherpa/src/sherpa.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -534,11 +534,20 @@ class SherpaProvider extends ProviderClass<WASocket> {
}
}

// Buscar siempre el que tenga formato @s.whatsapp.net (puede estar en remoteJid o remoteJidAlt)
const remoteJid = (messageCtx?.key as any)?.remoteJid
const remoteJidAlt = (messageCtx?.key as any)?.remoteJidAlt
const fromParse = remoteJid?.includes('@s.whatsapp.net')
? remoteJid
: remoteJidAlt?.includes('@s.whatsapp.net')
? remoteJidAlt
: remoteJid || remoteJidAlt

let payload = {
...messageCtx,
body: textToBody,
name: messageCtx?.pushName,
from: messageCtx?.key?.remoteJid,
from: baileyCleanNumber(fromParse),
}

if (messageCtx.message?.locationMessage) {
Expand Down