Closed
Bug 990020
Opened 10 years ago
Closed 10 years ago
[B2G][SMS] A MMS that has not been downloaded yet will display a "Missing SIM card" message after changing the SIM to a different valid one
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Tracking
(tracking-b2g:backlog, b2g-v1.4 affected)
People
(Reporter: julienw, Assigned: azasypkin)
References
()
Details
(Whiteboard: burirun1.4-1, burirun1.4-2[priority][sms-most-wanted])
Attachments
(1 file)
We need to handle the "SimNotMatchedError" error when retrieving a message. See below for the initial description. Currently, the displayed message will be the generic error message which is not very good because the generic message is more suited when sending a message. +++ This bug was initially created as a clone of Bug #981077 +++ Description: When there is an MMS attachment pending if the user switches the SIM card and tries to then download the MMS attachment the message "Missing SIM card" appears even though the new SIM card can be used. Essentially the message is inappropriate for the situation. Repro Steps: 1) Update a Buri to BuildID: 20140307040203 2) Go to Settings -> Messaging settings and turn Auto retrieve OFF. 3) Send an MMS from another device to the test device. 4) Open the message app to view the message, but do not download the attachment. 5) Power down the test device and change to another valid SIM. 6) Power back on the device and go to the message app. 7) Attempt to download the MMS attachment. Actual: The message "Missing SIM card" appears Expected: A message properly explaining why the attachment cannot be downloaded is displayed. 1.4 Environmental Variables: Device: Buri 1.4 MOZ BuildID: 20140307040203 Gaia: 04eb7996543f114133d1367f834a4d88b68c60ac Gecko: b0e7f63c2138 Version: 30.0a1 Firmware Version: v1.2-device.cfg Keywords: SMS Notes: Likely related to https://bugzilla.mozilla.org/show_bug.cgi?id=924178 Repro frequency: 100% Link to failed test case: https://moztrap.mozilla.org/manage/case/8275/ See attached: screenshot of message
Reporter | ||
Comment 1•10 years ago
|
||
NI Joe because we need to prioritize this in the 1.5 time frame.
Flags: needinfo?(jcheng)
Comment 2•10 years ago
|
||
already 1.5?, this will be triaged during comms team triage Thanks
Flags: needinfo?(jcheng)
Updated•10 years ago
|
status-b2g-v1.4:
--- → affected
Whiteboard: burirun1.4-1 → burirun1.4-1, burirun1.4-2
Comment 3•10 years ago
|
||
triage: add to 1.5 targetted list
Blocks: comms_2.0_targeted
blocking-b2g: 1.5? → backlog
Updated•10 years ago
|
Whiteboard: burirun1.4-1, burirun1.4-2 → burirun1.4-1, burirun1.4-2[priority]
Reporter | ||
Updated•10 years ago
|
Whiteboard: burirun1.4-1, burirun1.4-2[priority] → burirun1.4-1, burirun1.4-2[priority][sms-most-wanted]
Assignee | ||
Comment 4•10 years ago
|
||
Hey Jenny, I'm not sure whether you're right person to ask about it :), but could you please advise what title and text should be used for the error dialog explaining that the attachment cannot be downloaded because of the SIM mismatch? Thanks!
Assignee: nobody → azasypkin
Status: NEW → ASSIGNED
Flags: needinfo?(jelee)
(In reply to Oleg Zasypkin [:azasypkin] from comment #4) > Hey Jenny, > > I'm not sure whether you're right person to ask about it :), but could you > please advise what title and text should be used for the error dialog > explaining that the attachment cannot be downloaded because of the SIM > mismatch? > > Thanks! Hello Oleg :D There should be a professional tech writer to help on this. But here's my suggestion: "Unable to download. Please make sure the SIM card inserted is the one when this message was received." Thanks!
Flags: needinfo?(jelee)
Assignee | ||
Comment 6•10 years ago
|
||
(In reply to Jenny Lee from comment #5) > (In reply to Oleg Zasypkin [:azasypkin] from comment #4) > > Hey Jenny, > > > > I'm not sure whether you're right person to ask about it :), but could you > > please advise what title and text should be used for the error dialog > > explaining that the attachment cannot be downloaded because of the SIM > > mismatch? > > > > Thanks! > > Hello Oleg :D > There should be a professional tech writer to help on this. But here's my > suggestion: > "Unable to download. Please make sure the SIM card inserted is the one when > this message was received." > Thanks! Hey Jenny, Thanks! I've been just pointed out to Matej, who can help with it :) Hi Matej, Could you please confirm that the following error dialog text and title are OK for the case when user tries to download MMS content with the SIM different from one that was used to receive this MMS. Title: 'Unable to download.' Text: 'Please make sure the SIM card inserted is the one when this message was received.' Thanks!
Flags: needinfo?(Mnovak)
Comment 7•10 years ago
|
||
Hi Oleg, Here's what I'm thinking for this: Unable to download Please make sure the SIM card inserted is the one used to receive this message. How does that sound?
Flags: needinfo?(Mnovak)
Assignee | ||
Comment 8•10 years ago
|
||
(In reply to Matej Novak [:matej] from comment #7) > Hi Oleg, > > Here's what I'm thinking for this: > > Unable to download > Please make sure the SIM card inserted is the one used to receive this > message. > > How does that sound? Yeah, sounds good! Thanks!
Assignee | ||
Comment 9•10 years ago
|
||
Julien, This patch contains two commits, the first for the basic fix and the second one where I've tried to organize error code usage a bit. So it would be great to get your feedback on this. Thanks!
Attachment #8451456 -
Flags: review?(felash)
Reporter | ||
Comment 10•10 years ago
|
||
Comment on attachment 8451456 [details] [review] GitHub pull request URL I'm fine with the first commit but as discussed the refactoring is too complex for our needs. Let's extract the error informations in its own file, keeping some of the changes you did (the Map for example), and either keep ErrorDialog like it is now, or make it take the Map value as parameter. (I don't quite know my preference yet)
Attachment #8451456 -
Flags: review?(felash)
Assignee | ||
Comment 11•10 years ago
|
||
Comment on attachment 8451456 [details] [review] GitHub pull request URL (In reply to Julien Wajsberg [:julienw] from comment #10) > Comment on attachment 8451456 [details] [review] > GitHub pull request URL > > I'm fine with the first commit but as discussed the refactoring is too > complex for our needs. > > Let's extract the error informations in its own file, keeping some of the > changes you did (the Map for example), and either keep ErrorDialog like it > is now, or make it take the Map value as parameter. (I don't quite know my > preference yet) Ok, as we agreed I've moved refactoring commit to a separate bug 1035279 and set r+ for the patch with first commit only. Waiting for Travis... Thanks!
Attachment #8451456 -
Flags: review+
Assignee | ||
Comment 12•10 years ago
|
||
Master: https://github.com/mozilla-b2g/gaia/commit/97107ca63bad94b9238312869a3e360fc2dda037
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
You need to log in
before you can comment on or make changes to this bug.
Description
•