We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2016-10-07 15:04:13 +0200

Bug: corruption of long SMS on receipt

So this is a rarity, but I've now been able to identify it has definitely happening from multiple different senders: when I receive multi-part SMSs, very rarely the end of a past SMS (from the same sender so far) is tagged on to the current one.

Digging into commhistory.db, it's as if the old SMS was in a buffer, and the new one is written into that same buffer without shortening the length (or maybe putting in a new terminating null character?): the latest example is where I received a 306-character SMS this morning which has been stored with additionally characters 307-372 of another SMS from the same sender from August 2015. We've exchanged many SMSs in the interim.

Anyone else experience this?

Bug: corruption of long SMS on receipt

So this is a rarity, but I've now been able to identify it has definitely happening from multiple different senders: when I receive multi-part SMSs, very rarely the end of a past SMS (from the same sender so far) is tagged on to the current one.

Digging into commhistory.db, it's as if the old SMS was in a buffer, and the new one is written into that same buffer without shortening the length (or maybe putting in a new terminating null character?): the latest example is where I received a 306-character SMS this morning which has been stored with additionally characters 307-372 of another SMS from the same sender from August 2015. We've exchanged many SMSs in the interim.

Anyone else experience this?

Bug: corruption of long SMS on receipt

So this is a rarity, but I've now been able to identify it has definitely happening from multiple different senders: when I receive multi-part SMSs, very rarely the end of a past SMS (from the same sender so far) is tagged on to the current one.

Digging into commhistory.db, it's as if the old SMS was in a buffer, and the new one is written into that same buffer without shortening the length (or maybe putting in a new terminating null character?): the latest example is where I received a 306-character SMS this morning which has been stored with additionally characters 307-372 of another SMS from the same sender from August 2015. We've exchanged many SMSs in the interim.

Anyone else experience this?