Closed
Bug 887815
Opened 11 years ago
Closed 11 years ago
[SMS][MMS] receiving successful delivery report even though delivery report is OFF in settings
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Tracking
(blocking-b2g:leo+, firefox23 wontfix, firefox24 wontfix, firefox25 fixed, b2g18 fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 wontfix, b2g-v1.1hd fixed)
People
(Reporter: maat, Assigned: airpingu)
References
Details
(Whiteboard: MMS_TEF[fixed-in-birch])
Attachments
(3 files)
259.33 KB,
image/png
|
Details | |
1.17 KB,
patch
|
ctai
:
review+
|
Details | Diff | Splinter Review |
5.05 KB,
patch
|
airpingu
:
review+
|
Details | Diff | Splinter Review |
receiving successful delivery report even though delivery report is OFF in settings **PATH** 1) open message app 2) select new message 3) enter valid phone number into 'to field' 4) enter some text into the message field **EXPECTED** Message will be successfully delivered without notification **ACTUAL** Notification is given in the message thread that the message has been successfully delivered
Reporter | ||
Comment 1•11 years ago
|
||
N.B. ensuer that delivery report is OFF in settings before executing steps 1 to 4 build information: V1-train Gecko - 914243b Gaia - 477e572 build id - 20130627123702
blocking-b2g: --- → leo?
Whiteboard: MMS_TEF
Comment 3•11 years ago
|
||
I _think_ we have that bug already. gene, I think you know ?
Flags: needinfo?(gene.lian)
Whiteboard: MMS_TEF → MMS_TEF, dupeme
Comment 4•11 years ago
|
||
we should not do anything in gaia here, only gecko should not send the delivery report.
Component: Gaia::SMS → DOM: Device Interfaces
Product: Boot2Gecko → Core
Assignee | ||
Comment 5•11 years ago
|
||
(In reply to Julien Wajsberg [:julienw] from comment #4) > we should not do anything in gaia here, only gecko should not send the > delivery report. Indeed. There might be something wrong in the Gecko. I'll check it out. There should be nothing to do with the Gaia.
Flags: needinfo?(gene.lian)
Assignee | ||
Comment 6•11 years ago
|
||
This one should have been fixed after Bug 884969 and Bug 883095 landed. I'll double check with the latest b2g18 codes and come back with the results.
Comment 7•11 years ago
|
||
bug 883095 was uplifted the same day as this bug was reported, so probably it's a dupe.
Assignee | ||
Comment 8•11 years ago
|
||
I found out this still doesn't work during the very first time of usage. The settings shows delivery report is off but we'll still receive the delivery report. After toggling the settings to true or false, we can receive delivery report as expected. This is supposed to be a simple fix on the Gaia end during initialization. I can help with that.
Component: DOM: Device Interfaces → Gaia::SMS
OS: Mac OS X → Gonk (Firefox OS)
Product: Core → Boot2Gecko
Hardware: x86 → ARM
Whiteboard: MMS_TEF, dupeme → MMS_TEF
Assignee | ||
Comment 9•11 years ago
|
||
Hi dietrich, The delivery report mechanism is still not yet complete. Need your help to mark this as leo+. Btw, one question, what's the desired delivery report by default? On or off? I think it should be on. Right? Visible feature is supposed to be better.
Assignee: nobody → gene.lian
Flags: needinfo?(dietrich)
Comment 10•11 years ago
|
||
Hi Beatriz, Could you confirm the default value for delivery report? Thanks
Flags: needinfo?(brg)
Assignee | ||
Comment 11•11 years ago
|
||
It seems bug 884906 has already had a solution for this.
Comment 12•11 years ago
|
||
(In reply to Steve Chung from comment #10) > Hi Beatriz, Could you confirm the default value for delivery report? Thanks The default value for delivery report should be Off. Thanks.
Flags: needinfo?(brg)
Assignee | ||
Comment 13•11 years ago
|
||
OK. So we need to uplift Bug 875854 to b2g18 to fix this issue.
Depends on: 875854
Assignee | ||
Comment 14•11 years ago
|
||
If the ril.sms.requestStatusReport.enabled is not available, consider it as false by default.
Attachment #768837 -
Flags: review?(ctai)
Comment 15•11 years ago
|
||
Comment on attachment 768837 [details] [diff] [review] Patch Review of attachment 768837 [details] [diff] [review]: ----------------------------------------------------------------- Looks good to me.
Attachment #768837 -
Flags: review?(ctai) → review+
Assignee | ||
Comment 16•11 years ago
|
||
https://hg.mozilla.org/projects/birch/rev/12982b75bf28
Whiteboard: MMS_TEF → MMS_TEF[fixed-in-birch]
Assignee | ||
Comment 17•11 years ago
|
||
Waiting on leo+ to land this to b2g18.
Updated•11 years ago
|
blocking-b2g: leo? → leo+
Assignee | ||
Comment 18•11 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g18/rev/8d883cb49438
status-b2g18:
--- → fixed
status-b2g18-v1.0.0:
--- → wontfix
status-b2g18-v1.0.1:
--- → wontfix
status-b2g-v1.1hd:
--- → affected
Comment 19•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/12982b75bf28
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 20•11 years ago
|
||
So b2g18 has had busted Marionette testing since Friday due to this landing. What part of "if you push to b2g18, you must watch your push" isn't clear? Backed out. https://hg.mozilla.org/releases/mozilla-b2g18/rev/004e9cec737f https://tbpl.mozilla.org/php/getParsedLog.php?id=24705282&tree=Mozilla-B2g18
Flags: needinfo?(gene.lian)
Updated•11 years ago
|
Assignee | ||
Comment 21•11 years ago
|
||
So sorry about this... I'm over-confident with this fix. I'll watch out next time.
Flags: needinfo?(gene.lian)
Assignee | ||
Comment 22•11 years ago
|
||
Attachment #769658 -
Flags: review+
Assignee | ||
Comment 23•11 years ago
|
||
Reland: https://hg.mozilla.org/releases/mozilla-b2g18/rev/15923aca6e6d
Flags: needinfo?(dietrich)
Assignee | ||
Updated•11 years ago
|
Comment 24•11 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g18_v1_1_0_hd/rev/15923aca6e6d
status-firefox23:
--- → wontfix
status-firefox24:
--- → wontfix
status-firefox25:
--- → fixed
Target Milestone: --- → 1.1 QE4 (15jul)
Comment 25•11 years ago
|
||
Verified with unagi 07/03 v1-train build: Gecko-109f9e3 Gaia-2c40cce When delivery report is off, the double check does not appear next to the message sent.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•