touch-packages team mailing list archive

[Olga Kemmet <1372646@xxxxxxxxxxxxxxxxxx>]

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.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to history-service in Ubuntu.
https://bugs.launchpad.net/bugs/1372646

Title:
  Can't correct SMS number after entering it wrong once

Status in Telephony History Service:
  New
Status in Messaging App:
  Confirmed
Status in Telepathy Ofono:
  New
Status in history-service package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New
Status in telepathy-ofono package in Ubuntu:
  New
Status in history-service package in Ubuntu RTM:
  New
Status in messaging-app package in Ubuntu RTM:
  New
Status in telepathy-ofono package in Ubuntu RTM:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/history-service/+bug/1372646/+subscriptions