Closed Bug 881248 Opened 11 years ago Closed 11 years ago

[MMS] Multirecipient. A contact with >1 number must only render the relevant number (vs. rendering all)

Categories

(Firefox OS Graveyard :: Gaia::SMS, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(blocking-b2g:leo+, b2g18 verified, b2g-v1.1hd fixed)

VERIFIED FIXED
blocking-b2g leo+
Tracking Status
b2g18 --- verified
b2g-v1.1hd --- fixed

People

(Reporter: isabelrios, Assigned: rwaldron)

References

Details

(Whiteboard: MMS_TEF)

Attachments

(3 files)

Bug seen on Unagi with today's build (06/10)
Gecko-b518de0
Gaia-aa166a4

PROCEDURE
Have one contact with two different phone numbers.
1. Create a new MMS
2. Tap into the 'To' field and type the contact name
3. Select the contact once
4. Select the contact again but with the other phone number

EXPECTED
The MMS in the origin appears as a MMS sent to two numbers

ACTUAL
The MMS in the origin seems to have sent to four numbers (twice for each contact's number)
Assignee: nobody → waldron.rick
Summary: [MMS] Multirecipient. Adding the same contact with different number is not managed correctly → [MMS] Multirecipient. A contact with >1 number must only render the relevant number (vs. rendering all)
Attached file Fix for 881248
Attachment #760554 - Flags: review?(felash)
Comment on attachment 760554 [details] [review]
Fix for 881248

comments on the PR
Blocks: 880624
No longer blocks: 880624
Blocks: 882899
Comment on attachment 760554 [details] [review]
Fix for 881248

r=me with the latest nit
Attachment #760554 - Flags: review?(felash) → review+
Landed
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Landedhttps://github.com/mozilla-b2g/gaia/commit/6406b9a535b5fcd7143a6ccb58c03a3a7b4296c5
blocking-b2g: leo? → leo+
I was not able to uplift this bug to v1-train.  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, 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  6406b9a535b5fcd7143a6ccb58c03a3a7b4296c5
  <RESOLVE MERGE CONFLICTS>
  git commit
Flags: needinfo?(waldron.rick)
part of conflict comes from the fact that bug 876754 is not leo+. The other conflicts are because Bug 882899 and Bug 881716 are not uplifted yet, I'm updting flags there.
Requested leo on bug 876754.
Flags: needinfo?(waldron.rick)
uplifted master: 6406b9a535b5fcd7143a6ccb58c03a3a7b4296c5
to v1-train: e6a24c1c14b9a55d0ae69468cf1f3a396d7ea20c
v1.1.0hd: e6a24c1c14b9a55d0ae69468cf1f3a396d7ea20c
Verified with unagi v1-train 07/15 build:
Gecko-2b310a1
Gaia-d52ce22
ref ril
Status: RESOLVED → VERIFIED
Verified it's fixed on Leo V1.1 
When sending MMS to a one contact with 2 numbers, the MMS is sent and in the origin it shows as the MMS sent to the two different phone numbers

Environmental  Variables:
Build ID: 20130717070237
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/582e3a7018b0
Gaia: c506c50adaaebcf729ac3c27887ba2931ab79040
Platform Version: 18.1
RIL Version: 01.01.00.019.138
Attachment mime type: text/plain → text/x-github-pull-request
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: