Closed
Bug 861720
Opened 11 years ago
Closed 11 years ago
Phone number to contact mapping matches if the number is a proper substring
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Tracking
(blocking-b2g:tef+, b2g18 verified, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 verified)
People
(Reporter: MattN, Unassigned)
Details
(Keywords: b2g-testdriver, unagi)
STR: 1) Receive an SMS from a shortcode * Easy wasy with t-mobile is to receive send an SMS to your phone using their email gateway: 10digitphonenumber@tmomail.net 2) Look at the shortcode that the SMS was from (e.g. 3769) 3) Add a contact which happens to contain this number as a substring (e.g. +15553769555) and give it a name 4) Go back to the SMS message app Expected result: SMS app should continue to show the message is from 3769 (no contact mapping) Actual result: SMS app mistakenly matches the SMS from 3769 to the contact with number +15553769555 I have run into this many times with a few hundred contacts and random shortcodes from t-mobile. It's misleading and inaccurate which could cause users to think they are receiving messages from someone other than the actual sender. I am running v1.1 beta build 20130404070202 See also bug 857460 about ignoring formatting for phone number matches.
Reporter | ||
Comment 1•11 years ago
|
||
I think the code path is: apps/sms/js/thread_list_ui.js updateThreadWithContact > Contacts.findByString(number, function gotContact(contacts) { apps/sms/js/contacts.js Contacts.findByString > return this.findBy({ > filterBy: ['tel', 'givenName', 'familyName'], > filterOp: 'contains', Since we are using the "contains" operator here, +15553769555 is returned because it contains 3769. We should do additional checks that the number is a match by ignoring formatting (bug 857460) and then comparing the length or something similar. I also don't think we should be searching the names from this caller (since it's extra work) so it seems like there should be another function named "findByNumber" which only searches the "tel" field and could do these additional checks.
Comment 2•11 years ago
|
||
Hi, I think this could have an important impact, specially with short numbers typically used by operators. I nominate it for tef? Thanks! David
blocking-b2g: --- → tef?
Updated•11 years ago
|
blocking-b2g: tef? → tef+
Target Milestone: --- → 1.0.1 IOT1 (10may)
Comment 3•11 years ago
|
||
Etienne & Francisco, are dialer and SMS aligned in behaviour here? What do you think of this bug? Rob (I'm adding him on CC here) has offered UX input if required. Set needinfo on him if you'd like his help.
Flags: needinfo?(francisco.jordano)
Flags: needinfo?(etienne)
Comment 4•11 years ago
|
||
What we do in the dialer is that if a number is less than 7 characters long (ie. a short number [1]) we request an "equals" match. So we don't have this issue. [1] http://en.wikipedia.org/wiki/E.164
Flags: needinfo?(etienne)
Comment 5•11 years ago
|
||
I think that this was solved on bug 856991, so it's probably a matter of old build with the code not updated. Build is from 04/04 and the bug was solved on 25/04. Could you please try with a recent build, or update your gaia code?
Comment 6•11 years ago
|
||
Matt, can you try with a more recent build?
Flags: needinfo?(francisco.jordano) → needinfo?(mnoorenberghe+bmo)
Reporter | ||
Comment 7•11 years ago
|
||
The patch in bug 856991 only landed four days after I filed this bug. https://github.com/mozilla-b2g/gaia/commit/51931fee784c0a9e81fa5afc525007e8ad9f2340 I just received an updated beta v.1.1.0 build today and I can confirm that this is now fixed.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(mnoorenberghe+bmo)
Resolution: --- → FIXED
Comment 8•11 years ago
|
||
(In reply to Matthew N. [:MattN] from comment #7) > The patch in bug 856991 only landed four days after I filed this bug. > https://github.com/mozilla-b2g/gaia/commit/ > 51931fee784c0a9e81fa5afc525007e8ad9f2340 > > I just received an updated beta v.1.1.0 build today and I can confirm that > this is now fixed. Thanks, Matt!
Comment 9•11 years ago
|
||
I was not able to uplift this bug to v1-train and v1.0.1. If this bug has dependencies which are not marked in this bug, please comment on this bug. If this bug depends on patches that aren't approved for v1-train and v1.0.1, we need to re-evaluate the approval. Otherwise, if this is just a merge conflict, you might be able to resolve it with: git checkout v1-train git cherry-pick -x -m1 51931fee784c0a9e81fa5afc525007e8ad9f2340 <RESOLVE MERGE CONFLICTS> git commit git checkout v1.0.1 git cherry-pick -x $(git log -n1 v1-train --pretty=%H)
Comment 10•11 years ago
|
||
Hey, this was already uplifted in bug 856991
Comment 11•11 years ago
|
||
Verified fixed on Inari Build ID: 20130506070205 Kernel Date: Feb 21 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/ce67220b877d Gaia: 1e598d8842920d9e0b1743dc6fe9390bd5f6e2df and on Unagi Build ID: 20130506070204 Kernel Date: Dec 5 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/00c554abfc17 Gaia: 9377636cee5ac55b9f1d68f598afc7aadfbb2b00 When user enters a number that has some of the number attached to a name it will no longer automatically send to saved user. It will instead send to number entered in To field.
You need to log in
before you can comment on or make changes to this bug.
Description
•