Old SMS text is sent instead of new text

asked 2014-03-26 00:48:34 +0300

hagen gravatar image

updated 2017-09-15 18:13:31 +0300

Mohjive gravatar image

When I send an SMS message, the receiver sometimes gets the text of an old message from the same conversation. Then the only way to send the new text is to delete the whole conversation.

I have the newest Sailfish version, but the problem also occurred in the earlier versions.

Still present in (Jämsänjoki)

edit retag flag offensive close delete


Also of interest: [Bug] Received SMS mixed together and Problems with "long" SMS messages (>160 chars.) including emojis

Problems are existing with receiving and sending!

I have < 1024 messages with a contact. Received a message which made no sense (sender likely placed emojis in it). The beginning is missing and I just received the end.

Even worse:

Contact with some more messages, don't know if > 1024 but I don't think so. I sent a long message. It's in the history exactly as I wrote it. But the recipient got the begin with content from a sms I've sent 5 months ago, and the end with content of the actual one. Thats a no go which can have terrible consequences depending on whats getting mixed up here.

So has anyone of you opened a ticket? Is Jolla aware of this terrible bugs?

It could be a reason for me to switch mobile os. Because I now feel very insecure and uncomfortable as I don't know what content my device will really send.

A day or so after the receive bug appeared about every second message didn't get sent (correctly) (provider answered with an automated sms that it could not be transfered). To overcome this the message had to be written new i.e. with copy and paste. I backed up and imported my messages with the backup function after that. This solved the provider does not "want" to send issue. But the bug of sending wrong content happened after that, so with a relatively new imported database. Receiving bug was while on 1.1.4, sending bug on 1.1.6!

This all happened after I used xmpp for some days. But this messages were already deleted and the protocol was deactivated.

Halo2 ( 2015-07-31 19:05:52 +0300 )edit

I started a poll to see if it's related to many messages or database tempering. Please vote.

Yo ( 2015-08-19 18:44:04 +0300 )edit

I think this is actually the same problem as described in https://together.jolla.com/question/102020/bug-received-sms-mixed-together/

It would be a different issue if the receiver got an old message in entirety, rather than an old portion mingled with a new portion. @hagen: Can you confirm if the old content is always a portion of the new message, or if it is ever the case than an entire old message is received again?

MattVogt ( 2015-10-02 01:44:51 +0300 )edit

@MattVogt: The problem has (as far as I can tell) not reoccurred for me for quite a while. I thought it might have been solved with some Sailfish update. My problem here is that I hardly send any SMS messages (I usually use WhatsApp except for the few people who do not have a smartphone). And also the receiver has to actually tell me that they received an old message. But as I was told in the past, the receiver just got the exact old text again and again. We could only have a real conversation again after I deleted the message history with that person.

hagen ( 2015-10-11 12:36:14 +0300 )edit

@hagen: thanks for the update. That does indeed sound like a different problem - the 'mixed together' error becomes impossible to trigger once the old message fragment has been delivered as part of a new incoming message, so it isn't possible to receive the same message again and again.

MattVogt ( 2015-10-12 02:00:41 +0300 )edit