[Bug] Messages with multiple attachments or parts display out of order #3
Comments
|
Here is another example with the same conversation on the 3.1.5 Android app and an iOS 14.5 device |
|
Do you know of a way to consistently reproduce this bug? |
|
I would do so by sending an attachment together with a text caption directly from an iOS or macOS device. Afterwards, receive a tapback on either the attachment, caption, or both, and it should show up differently in AirMessage than it does on native iMessage. |
|
Thanks, I'll take a look at this tomorrow |
|
Okay, so one issue is that particularly on macOS, you're able to insert attachments at any point within the message and have the text split accordingly. However, I'm not sure how this is accounted for in the messages database.
|
|
That's a good point. You can do this on iOS too if you paste in the attachments instead of actually, well, attaching them. I hadn't considered that use case. |
Regarding this comment, I ran a test that mimicked this behavior on iOS. Below is the conversation on iOS UPDATE - Here is some message information that I got from MyMessage {
"id": "28935DBA-A57E-485E-9442-10FBAD3A3C95",
"fromMe": true,
"isTypingMessage": false,
"description": "Here is a message that has images intermittently scattered throughout it",
"flags": 1085445,
"fileTransferIDs": [
"49CA2847-DF32-4D66-9857-7163EE1FCE49",
"9C606BB6-2443-4101-A55A-8E2610D08988",
"00A6CB41-165B-43B8-881F-59D725515B36"
],
"chatID": "*recipient*",
"time": 1620776404411,
"timeRead": 0,
"isSOS": false,
"timeDelivered": 1620776405263.5593,
"isAudioMessage": false,
"isCancelTypingMessage": false,
"items": [
{
"type": "text",
"payload": {
"id": "p:0/28935DBA-A57E-485E-9442-10FBAD3A3C95",
"chatID": "*recipient*",
"parts": [
{
"type": "text",
"string": "Here is a message"
}
],
"fromMe": true,
"time": 1620776404411,
"text": "Here is a message"
}
},
{
"type": "attachment",
"payload": {
"metadata": {
"size": {
"width": 200,
"height": 200
},
"id": "49CA2847-DF32-4D66-9857-7163EE1FCE49",
"filename": "IMG_1752.png",
"uti": "public.png",
"mime": "image/png"
},
"id": "p:1/28935DBA-A57E-485E-9442-10FBAD3A3C95",
"chatID": "*recipient*",
"transferID": "49CA2847-DF32-4D66-9857-7163EE1FCE49",
"fromMe": true,
"time": 1620776404411
}
},
{
"type": "text",
"payload": {
"id": "p:2/28935DBA-A57E-485E-9442-10FBAD3A3C95",
"chatID": "*recipient*",
"parts": [
{
"type": "text",
"string": "that has images"
}
],
"fromMe": true,
"time": 1620776404411,
"text": "that has images"
}
},
{
"type": "attachment",
"payload": {
"metadata": {
"size": {
"width": 200,
"height": 200
},
"id": "9C606BB6-2443-4101-A55A-8E2610D08988",
"filename": "IMG_3897.png",
"uti": "public.png",
"mime": "image/png"
},
"id": "p:3/28935DBA-A57E-485E-9442-10FBAD3A3C95",
"chatID": "*recipient*",
"transferID": "9C606BB6-2443-4101-A55A-8E2610D08988",
"fromMe": true,
"time": 1620776404411
}
},
{
"type": "text",
"payload": {
"id": "p:4/28935DBA-A57E-485E-9442-10FBAD3A3C95",
"chatID": "*recipient*",
"parts": [
{
"type": "text",
"string": "intermittently scattered"
}
],
"fromMe": true,
"time": 1620776404411,
"text": "intermittently scattered"
}
},
{
"type": "attachment",
"payload": {
"metadata": {
"size": {
"width": 200,
"height": 200
},
"id": "00A6CB41-165B-43B8-881F-59D725515B36",
"filename": "IMG_4390.png",
"uti": "public.png",
"mime": "image/png"
},
"id": "p:5/28935DBA-A57E-485E-9442-10FBAD3A3C95",
"chatID": "*recipient*",
"transferID": "00A6CB41-165B-43B8-881F-59D725515B36",
"fromMe": true,
"time": 1620776404411
}
},
{
"type": "text",
"payload": {
"id": "p:6/28935DBA-A57E-485E-9442-10FBAD3A3C95",
"chatID": "*recipient*",
"parts": [
{
"type": "text",
"string": "throughout it"
}
],
"fromMe": true,
"time": 1620776404411,
"text": "throughout it"
}
}
],
"service": "iMessage",
"timePlayed": 0,
"sender": "*me*",
"isDelivered": true
} |
|
As per @CSab6482 's request, the way to solve this is to deserialize attributedBody (which you've already done) and look at each component inside its The attributedBody also provides data for mentions within texts. |
This is helpful, thank you! |
The message I sent with the picture of Thanos and the text caption were sent from an iOS device.
I have pasted Tagavari's question from my reddit post, along with my answer.
It is the same message/a mixed message.
Is the Protocol 5.2 sorting parameter useful for this issue, or no?
This particular photo of Thanos has been an issue that I have reported on quite a lot.
See here, here, here, here, and here.
{ "id": "D3DBDAD8-5EEE-4D72-ADB7-20A74501706D", "fromMe": true, "isTypingMessage": false, "description": "We'll show up and he'll be like", "flags": 1081349, "fileTransferIDs": [ "72D48466-A535-4C93-AA78-6791A8AB53F1" ], "chatID": "chat526745548997352517", "time": 1615577622383.0002, "timeRead": 0, "isSOS": false, "timeDelivered": 0, "isAudioMessage": false, "isCancelTypingMessage": false, "items": [ { "type": "attachment", "payload": { "metadata": { "size": { "width": 500, "height": 255 }, "id": "72D48466-A535-4C93-AA78-6791A8AB53F1", "filename": "AE5727AE-29A7-4E84-B537-17AFD35FEB41.gif", "uti": "com.compuserve.gif", "mime": "image/gif" }, "id": "p:0/D3DBDAD8-5EEE-4D72-ADB7-20A74501706D", "chatID": "chat526745548997352517", "transferID": "72D48466-A535-4C93-AA78-6791A8AB53F1", "fromMe": true, "time": 1615577622383.0002 } }, { "type": "text", "payload": { "chatID": "chat526745548997352517", "fromMe": true, "parts": [ { "type": "text", "string": "We'll show up and he'll be like" } ], "id": "p:1/D3DBDAD8-5EEE-4D72-ADB7-20A74501706D", "time": 1615577622383.0002, "text": "We'll show up and he'll be like", "acknowledgments": [ { "chatID": "chat526745548997352517", "sender": "*my friend's email*", "associatedID": "p:1/D3DBDAD8-5EEE-4D72-ADB7-20A74501706D", "id": "am:F0716C13-6871-4286-A4A6-3CF3FB0B25CD", "fromMe": false, "time": 1615577636093.2012, "acknowledgmentType": 2003 } ] } } ], "service": "iMessage", "timePlayed": 0, "sender": "e:*my email*", "isDelivered": false }The text was updated successfully, but these errors were encountered: