EvolutionAPI
[BUG] remoteJid is differenten than the real whatsaap number
Welcome!
- [x] Yes, I have searched for similar issues on GitHub and found none.
What did you do?
Versión de Evolution API: v2.2.3 and older versions When a message is received from a new WhatsApp contact using an Android Whatsapp number Evolution API attempts to create a contact using the LID as the phone number, (remoteJid: '154417159582282@lid',) instead of the real number ([email protected]) causing the response message not delivered
What did you expect?
Evolution API should resolve the LID to a real phone number ([email protected]) before sending to chatwoot or any other app.
What did you observe instead of what you expected?
With iphone the phone number is correct. It only happens when the sender has an Android phone.
Screenshots/Videos
No response
Which version of the API are you using?
v2.2.1 and tried latest too
What is your environment?
Windows
Other environment specifications
easypanel on hostinger VPS
If applicable, paste the log output
[Evolution API] [BNSt] v2.1.1 184 - Sat Sep 06 2025 20:31:33 LOG [ChannelStartupService] [object]
{
key: MessageKey {
remoteJid: '[email protected]',
fromMe: true,
id: '3EB073ADB8DD86D47345ABD99D2213513E739793'
},
pushName: '',
message: {
conversation: '¡Hola! Bienvenido/a a BNS. Soy XXXX, tu asistente personal. ¿Qué te gustaría hacer hoy?\n' +
'\n' +
'1. Ver información de servicios\n' +
'2. Hacer una reserva\n' +
'3. Otros temas (cancelar, etc.)\n' +
'\n' +
'Por favor, responde con el número de la opción que prefieras.'
},
contextInfo: null,
messageType: 'conversation',
messageTimestamp: 1757201492,
instanceId: '2e9e87e9-bf54-4022-9ad0-10ea289320be',
source: 'unknown'
}
[Evolution API] v2.1.1 184 - Sat Sep 06 2025 20:31:33 VERBOSE [CacheEngine] [string] RedisCache initialized for he
[Evolution API] v2.1.1 184 - Sat Sep 06 2025 20:31:33 VERBOSE [CacheService] [string] cacheservice created using cache engine: Vt
[Evolution API] v2.1.1 184 - Sat Sep 06 2025 20:31:33 VERBOSE [CacheEngine] [string] RedisCache initialized for he
[Evolution API] v2.1.1 184 - Sat Sep 06 2025 20:31:33 VERBOSE [CacheService] [string] cacheservice created using cache engine: Vt
[Evolution API] [BNS] v2.1.1 184 - Sat Sep 06 2025 20:34:02 LOG [ChannelStartupService] [object]
{
key: {
remoteJid: '154417159582282@lid',
fromMe: false,
id: 'AC480D75BAFBB29B688D9F897E590325',
participant: undefined
},
pushName: 'Pepinita Mandarin',
message: {
conversation: 'Hola',
messageContextInfo: MessageContextInfo {
deviceListMetadata: [DeviceListMetadata],
deviceListMetadataVersion: 2,
messageSecret: [Uint8Array]
}
},
contextInfo: undefined,
messageType: 'conversation',
messageTimestamp: 1757201641,
instanceId: '2e9e87e9-bf54-4022-9ad0-10ea289320be',
source: 'android',
chatwootMessageId: 3426,
chatwootInboxId: 2,
chatwootConversationId: 23
}
Additional Notes
No response
I am using version: 2.2.3 and it happened to me with only one number, but I noticed it was after I connected this number to EVO. For my users, everything is normal. How many remoteIds have already been changed in your flow?
Hi! I’m experiencing the same problem very frequently. When the sender is using Android, EvolutionAPI sends the remoteJid with @ lid, instead of the correct @s.whatsapp.net, which causes Chatwoot to create a new (invalid) contact and breaks the conversation flow.
Did you manage to find a workaround or solution for this issue? Thanks in advance 🙏
I have the same problem, messages are not being sent because of this.
before it was like this: [email protected]
now: remoteJid:127950449590133@lid
anyone has solved it ?
For the moment I migrated to EvoAPI Cloud and the issue has not happened again so far.
segui esse tutorial e resolveu meu caso, se alguem tiver o mesmo problema só fazer isso. https://www.youtube.com/watch?v=FueG-JnJBeo
I've solved it putting the following java script code into a set node:
value1: message.chatId
type: string
value2 (Expression): {{
($json.body.data.key.remoteJid && $json.body.data.key.remoteJid.endsWith('@s.whatsapp.net'))
? $json.body.data.key.remoteJid
: ($json.body.data.key.remoteJidAlt && $json.body.data.key.remoteJidAlt.endsWith('@s.whatsapp.net'))
? $json.body.data.key.remoteJidAlt
: undefined
}}
I encounter the same problem, im using evolution with type-bot integration and it completely messes up the flow when I receive a @lid instead of the regular jid. is there anyway I can get the jid when a lid arrives via typebot?
Issues relacionadas: https://github.com/EvolutionAPI/evolution-api/issues/1872 https://github.com/EvolutionAPI/evolution-api/issues/2267
