Can't correct SMS number after entering it wrong once

Bug #1372646 reported by Michael Zanetti
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
telepathy-ofono
Fix Released
Undecided
Unassigned
history-service (Ubuntu)
Confirmed
Undecided
Gustavo Pichorim Boiko
history-service (Ubuntu RTM)
New
Undecided
Gustavo Pichorim Boiko
messaging-app (Ubuntu)
Confirmed
High
Tiago Salem Herrmann
messaging-app (Ubuntu RTM)
New
Undecided
Unassigned
telepathy-ofono (Ubuntu)
Fix Released
Undecided
Unassigned
telepathy-ofono (Ubuntu RTM)
New
Undecided
Unassigned

Bug Description

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 +491791234567
* 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.

Related branches

Bill Filler (bfiller)
Changed in messaging-app:
importance: Undecided → High
status: New → Confirmed
assignee: nobody → Tiago Salem Herrmann (tiagosh)
tags: added: rtm14 touch-2014-10-25
Revision history for this message
Victor Tuson Palau (vtuson) wrote :

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?

Revision history for this message
Victor Tuson Palau (vtuson) wrote :

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

Bill Filler (bfiller)
tags: added: ww03
Bill Filler (bfiller)
tags: removed: ww03
Changed in history-service (Ubuntu):
assignee: nobody → Gustavo Pichorim Boiko (boiko)
Changed in history-service (Ubuntu RTM):
assignee: nobody → Gustavo Pichorim Boiko (boiko)
Revision history for this message
Olga Kemmet (olga-kemmet) wrote :

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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in telepathy-ofono (Ubuntu):
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in history-service (Ubuntu):
status: New → Confirmed
Changed in messaging-app (Ubuntu):
status: New → Confirmed
no longer affects: messaging-app (Ubuntu)
affects: messaging-app → messaging-app (Ubuntu)
no longer affects: history-service (Ubuntu)
affects: history-service → history-service (Ubuntu)
Changed in history-service (Ubuntu):
assignee: nobody → Gustavo Pichorim Boiko (boiko)
status: New → Confirmed
Changed in history-service (Ubuntu):
status: New → Confirmed
Changed in telepathy-ofono:
status: New → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.