Can't correct SMS number after entering it wrong once

[Michael Zanetti]

Steps to reproduce (example, I suspect more number combinations are possible to reproduce):

* Using the bottom edge, write a new SMS to a foreign number which is not stored to your address book, but omit the country code. Eg, 01791234567
* Wait for the SMS delivery to fail.
* Go back to the conversations list and use the bottom edge to start writing a new SMS. enter the same number again, this time including the country code. eg [phone]
* The second SMS will be grouped with the first one and the first SMS's number will be used for the second SMS too causing all attempts to fail again.

This does not recover after clearing the conversation. dbus-monitor always shows HistoryService bringing back the old wrong number. Also the conversation's header will revert to the old number after exiting and re-entering the conversation.

[Victor Tuson Palau (vtuson)]

Hi Bill,

I think this needs to be critical. One use case that will trigger this bug will be if I am abroad roaming, all my usual numbers are unlikely to have the country code in, which means I will not be able to text anyone?

[Victor Tuson Palau (vtuson)]

Joe tested this and seems to work for him, can we validate that this is a real bug?

[Olga Kemmet (olga-kemmet)]

If it helps, this is how it works on the iPhone, sending a message to a number with and without the country code (UK -> Germany).

Both message appear as sent, I do not get any alert or notification that the message without the country code was not delivered. The messages are not grouped either.
However, the message without the country code never arrives...the one with the country code does. That is not exactly a good UX so I think we can do something better.

[Launchpad Janitor (janitor)]

This bug was fixed in the package telepathy-ofono - 0.2+15.04.20150331-0ubuntu1

---------------
telepathy-ofono (0.2+15.04.20150331-0ubuntu1) vivid; urgency=medium

  [ Tiago Salem Herrmann ]
  * Don't try to compare phone numbers, otherwise channels with wrong
    handles can be mistakenly reused when not intended. (LP: #1372646)
 -- CI Train Bot <email address hidden> Tue, 31 Mar 2015 17:56:15 +0000

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sebastien Bacher (seb128)]

is that issue resolved? should the remaining components be marked invalid then?