touch-packages team mailing list archive

[Bill Filler <1476833@xxxxxxxxxxxxxxxxxx>]

@tiagosh
Can you check if this is bug with libphonenumber or parsing we are doing? Perhaps the move to libphonenumber everywhere will fix it?

** Also affects: canonical-devices-system-image
   Importance: Undecided
       Status: New

** Changed in: address-book-app (Ubuntu)
     Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

** Changed in: address-book-app (Ubuntu)
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
    Milestone: None => ww34-2015

** Changed in: canonical-devices-system-image
     Assignee: (unassigned) => Bill Filler (bfiller)

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

** Also affects: telephony-service (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: telephony-service (Ubuntu)
     Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh)

** No longer affects: address-book-app (Ubuntu)

** Changed in: telephony-service (Ubuntu)
   Importance: Undecided => High

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

Title:
  wrong contact name is displayed for phone number

Status in Canonical System Image:
  New
Status in telephony-service package in Ubuntu:
  New

Bug description:
  In my address book I have two contacts with very similar numbers.
  (last 6 digits changed in the example)

  Person A:  +352 661 123456
  Person B:  +352 691 123456

  When I receive a call or try to compose a message to Person B, the
  phone always displays the name of Person A. The same happens in call
  records.

  The only way to have the name of Person B displayed upon calls or
  message sending is to delete Person A from the address book.

  This is very strange, because phone numbers are prefix codes, thus
  ignoring a leading digit in a phone number seems like the wrongest
  thing to do in this context.

  The bug is still present in the current MX4 image (revision 3)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1476833/+subscriptions