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
Our iOS application working fine if we are running normally, but if we are decrypting xmppmessage from notification module(a service extension), failed to decrypt OMEMO message.
forwardedMessage : <message xmlns="jabber:client" from="eb1ece2c-ddf4-4c71-a08d-3ab263282ef5@xmpp.mydomain.co.in/+911234567890" type="chat" to="4f1b2d35-ece6-4c10-91a3-b14bb6242e12@xmpp.mydomain.co.in" id="68ED74C0-D12E-4DF1-BFA1-D243FCE0D7F2"><store xmlns="urn:xmpp:hints"></store><encrypted xmlns="eu.siacs.conversations.axolotl"><header sid="3290964"><key rid="13159405">MwohBTVSW4L7PHrWgsZatH7IIclJfLTWkVZU3CHqfO+mps5lEAsYACIwVED90w9D3BIZaPyNiSN/QzC+Ozc+eCCqyVBB9iwMlAMImciMthLZYtmXA1whxuLPtEQXGL62o4w=</key><iv>uCA2esi9yEAl6XCr8a8bWA==</iv></header><payload>oME=</payload></encrypted><body>I sent you an OMEMO encrypted message but your client doesn’t seem to support that. Find more information on https://conversations.im/omemo</body><markable xmlns="urn:xmpp:chat-markers:0"></markable><message_type xmlns="jabber:message:type">0</message_type><Caption></Caption><request xmlns="urn:xmpp:receipts"></request><delay xmlns="urn:xmpp:delay" stamp="2024-01-03T10:13:11Z" from="eb1ece2c-ddf4-4c71-a08d-3ab263282ef5@xmpp.mydomain.co.in/+911234567890"></delay></message>
originalMessage: <message xmlns="jabber:client" from="4f1b2d35-ece6-4c10-91a3-b14bb6242e12@xmpp.mydomain.co.in" to="4f1b2d35-ece6-4c10-91a3-b14bb6242e12@xmpp.mydomain.co.in/+910123456789" id="fd774bc6-f868-40a8-829c-bf5f9e8c8528"><result xmlns="urn:xmpp:mam:2" queryid="FE3E8DE2-2C91-41E4-A913-8747EF85E65B" id="C3G7RJ1PUIG1"><forwarded xmlns="urn:xmpp:forward:0"><delay xmlns="urn:xmpp:delay" stamp="2024-01-03T10:13:11Z" from="eb1ece2c-ddf4-4c71-a08d-3ab263282ef5@xmpp.mydomain.co.in/+911234567890"></delay><message xmlns="jabber:client" from="eb1ece2c-ddf4-4c71-a08d-3ab263282ef5@xmpp.mydomain.co.in/+911234567890" type="chat" to="4f1b2d35-ece6-4c10-91a3-b14bb6242e12@xmpp.mydomain.co.in" id="68ED74C0-D12E-4DF1-BFA1-D243FCE0D7F2"><store xmlns="urn:xmpp:hints"></store><encrypted xmlns="eu.siacs.conversations.axolotl"><header sid="3290964"><key rid="13159405">MwohBTVSW4L7PHrWgsZatH7IIclJfLTWkVZU3CHqfO+mps5lEAsYACIwVED90w9D3BIZaPyNiSN/QzC+Ozc+eCCqyVBB9iwMlAMImciMthLZYtmXA1whxuLPtEQXGL62o4w=</key><iv>uCA2esi9yEAl6XCr8a8bWA==</iv></header><payload>oME=</payload></encrypted><body>I sent you an OMEMO encrypted message but your client doesn’t seem to support that. Find more information on https://conversations.im/omemo</body><markable xmlns="urn:xmpp:chat-markers:0"></markable><message_type xmlns="jabber:message:type">0</message_type><Caption></Caption><request xmlns="urn:xmpp:receipts"></request><delay xmlns="urn:xmpp:delay" stamp="2024-01-03T10:13:11Z" from="eb1ece2c-ddf4-4c71-a08d-3ab263282ef5@xmpp.mydomain.co.in/+911234567890"></delay></message></forwarded></result></message>
The text was updated successfully, but these errors were encountered:
Hi Experts, Please help us to come out from this:
Our iOS application working fine if we are running normally, but if we are decrypting xmppmessage from notification module(a service extension), failed to decrypt OMEMO message.
this function not working :
Logs:
Failed to decrypt OMEMO message:
forwardedMessage :
<message xmlns="jabber:client" from="eb1ece2c-ddf4-4c71-a08d-3ab263282ef5@xmpp.mydomain.co.in/+911234567890" type="chat" to="4f1b2d35-ece6-4c10-91a3-b14bb6242e12@xmpp.mydomain.co.in" id="68ED74C0-D12E-4DF1-BFA1-D243FCE0D7F2"><store xmlns="urn:xmpp:hints"></store><encrypted xmlns="eu.siacs.conversations.axolotl"><header sid="3290964"><key rid="13159405">MwohBTVSW4L7PHrWgsZatH7IIclJfLTWkVZU3CHqfO+mps5lEAsYACIwVED90w9D3BIZaPyNiSN/QzC+Ozc+eCCqyVBB9iwMlAMImciMthLZYtmXA1whxuLPtEQXGL62o4w=</key><iv>uCA2esi9yEAl6XCr8a8bWA==</iv></header><payload>oME=</payload></encrypted><body>I sent you an OMEMO encrypted message but your client doesn’t seem to support that. Find more information on https://conversations.im/omemo</body><markable xmlns="urn:xmpp:chat-markers:0"></markable><message_type xmlns="jabber:message:type">0</message_type><Caption></Caption><request xmlns="urn:xmpp:receipts"></request><delay xmlns="urn:xmpp:delay" stamp="2024-01-03T10:13:11Z" from="eb1ece2c-ddf4-4c71-a08d-3ab263282ef5@xmpp.mydomain.co.in/+911234567890"></delay></message>
originalMessage:
<message xmlns="jabber:client" from="4f1b2d35-ece6-4c10-91a3-b14bb6242e12@xmpp.mydomain.co.in" to="4f1b2d35-ece6-4c10-91a3-b14bb6242e12@xmpp.mydomain.co.in/+910123456789" id="fd774bc6-f868-40a8-829c-bf5f9e8c8528"><result xmlns="urn:xmpp:mam:2" queryid="FE3E8DE2-2C91-41E4-A913-8747EF85E65B" id="C3G7RJ1PUIG1"><forwarded xmlns="urn:xmpp:forward:0"><delay xmlns="urn:xmpp:delay" stamp="2024-01-03T10:13:11Z" from="eb1ece2c-ddf4-4c71-a08d-3ab263282ef5@xmpp.mydomain.co.in/+911234567890"></delay><message xmlns="jabber:client" from="eb1ece2c-ddf4-4c71-a08d-3ab263282ef5@xmpp.mydomain.co.in/+911234567890" type="chat" to="4f1b2d35-ece6-4c10-91a3-b14bb6242e12@xmpp.mydomain.co.in" id="68ED74C0-D12E-4DF1-BFA1-D243FCE0D7F2"><store xmlns="urn:xmpp:hints"></store><encrypted xmlns="eu.siacs.conversations.axolotl"><header sid="3290964"><key rid="13159405">MwohBTVSW4L7PHrWgsZatH7IIclJfLTWkVZU3CHqfO+mps5lEAsYACIwVED90w9D3BIZaPyNiSN/QzC+Ozc+eCCqyVBB9iwMlAMImciMthLZYtmXA1whxuLPtEQXGL62o4w=</key><iv>uCA2esi9yEAl6XCr8a8bWA==</iv></header><payload>oME=</payload></encrypted><body>I sent you an OMEMO encrypted message but your client doesn’t seem to support that. Find more information on https://conversations.im/omemo</body><markable xmlns="urn:xmpp:chat-markers:0"></markable><message_type xmlns="jabber:message:type">0</message_type><Caption></Caption><request xmlns="urn:xmpp:receipts"></request><delay xmlns="urn:xmpp:delay" stamp="2024-01-03T10:13:11Z" from="eb1ece2c-ddf4-4c71-a08d-3ab263282ef5@xmpp.mydomain.co.in/+911234567890"></delay></message></forwarded></result></message>
The text was updated successfully, but these errors were encountered: