Closed
Bug 911026
Opened 11 years ago
Closed 11 years ago
B2G SMS: regression in bug 899885 made SMS-DELIVER-REPORT unavailable
Categories
(Firefox OS Graveyard :: RIL, defect)
Tracking
(blocking-b2g:koi+, firefox26 fixed)
Tracking | Status | |
---|---|---|
firefox26 | --- | fixed |
People
(Reporter: echu, Assigned: ctai)
References
Details
(Whiteboard: [FT:RIL])
Attachments
(3 files)
There is no tick icon next to sent message even delivery report is on. Due to no UI indicator, I cannot tell whether no delivery report is received or it's SMS UI issue.
* Build Number
Gaia mozillaorg/master - 09cfa8afaf88b49fc58ee33ec29071038b7cea2c
Gecko mozillaorg/master - 6e7aba3837664574da9fafb9f4ff017276e500ba
BuildID 20130829061633
Version 26.0a1
* Reproduce Steps
1. Enable delivery report
2. Send a sms to other device.
* Expected Result
Tick icon will be seen on DUT in the message just sent after it's received by MT side.
* Actual Result
No tick icon.
* Occurrence rate
100%
Comment 1•11 years ago
|
||
Steve probably knows.
Comment 2•11 years ago
|
||
I don't have the target device wasabi right now, but I found another problem on unagi while updating the message database:
[JavaScript Error: "NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIMobileMessageService.createSmsMessage]" {file: "jar:file:///system/b2g/omni.ja!/components/MobileMessageDatabaseService.js" line: 818}]
This error occurs while database updating the message deliveryStatus to delivery success. It will cause the message unable to save into database and no event dispatched to gaia for sure. For you refresh the message lit again, the messsage should be updated to delivery success will disappear in current build. Need gecko devs help for further investigation.
Assignee: nobody → schung
Flags: needinfo?(vyang)
Flags: needinfo?(gene.lian)
Updated•11 years ago
|
Assignee: schung → nobody
Comment 3•11 years ago
|
||
Sadly, I'm going to have PTOs and not be available until 9/5. Could Ctai help with this? Thanks!
Flags: needinfo?(gene.lian)
Updated•11 years ago
|
Component: Gaia::SMS → DOM: Device Interfaces
Flags: needinfo?(vyang)
Product: Boot2Gecko → Core
Updated•11 years ago
|
Assignee: nobody → vyang
Assignee | ||
Comment 4•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Attachment #798386 -
Flags: review?(vyang)
Updated•11 years ago
|
Attachment #798386 -
Flags: review?(vyang) → review+
Assignee | ||
Updated•11 years ago
|
Assignee: vyang → ctai
Updated•11 years ago
|
Comment 5•11 years ago
|
||
Comment 6•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
Hi all,
I can still reproduce the issue with today's build, could you check if it's landed already?
Wasabi:
Gaia: 37bcf182902ce19aba99d8f381cfecdd161d6d8a
Gecko: 99509409adbd6c3063f6de5462a6a2797f2e4c47
BuildID 20130904062051
Version 26.0a1
Comment 8•11 years ago
|
||
(In reply to echu from comment #7)
> Hi all,
>
> I can still reproduce the issue with today's build, could you check if it's
> landed already?
Yes, it's already included in that Gecko commit and this does work for me.
Comment 9•11 years ago
|
||
Thanks Ctai and Vicamo!
Btw, I just found there is another tiny spot at:
if (response.errorMsg) {
...
switch (message.errorMsg) { --> wrong!
...
}
...
}
which is a similar issue. Could we reopen this bug to fix that or just fire a separate bug? Either works for me. Thanks!
Updated•11 years ago
|
Flags: needinfo?(ctai)
Assignee | ||
Comment 10•11 years ago
|
||
There is already a bug about what you are talking about.
Please see Bug 911690.
(In reply to Gene Lian [:gene] (please use needinfo?) from comment #9)
> Thanks Ctai and Vicamo!
>
> Btw, I just found there is another tiny spot at:
>
> if (response.errorMsg) {
> ...
> switch (message.errorMsg) { --> wrong!
> ...
> }
> ...
> }
>
> which is a similar issue. Could we reopen this bug to fix that or just fire
> a separate bug? Either works for me. Thanks!
Flags: needinfo?(ctai)
Reporter | ||
Comment 11•11 years ago
|
||
Hi Vicamo,
I still can't get delivery icon on today's build, can you check the log?
Gaia: f2ca2f21e75b7e1db4183960f69810422295c21f
Gecko: 2a2ff267b86346ae80e453a814c442da82583ab1
BuildID 20130905062051
Version 26.0a1
Reporter | ||
Comment 12•11 years ago
|
||
Comment 13•11 years ago
|
||
In attachment 800547 [details] it has:
RIL Worker[0]: Handling parcel as REQUEST_CDMA_SEND_SMS
The solution we had is for GSM phones. CDMA SMS has no DELIVER-REPORT support yet.
Flags: needinfo?(vyang)
Updated•11 years ago
|
Summary: [wasabi][SMS] There is no tick icon next to the message sent after enabling "Delivery reports". → B2G SMS: regression in bug 899885 made SMS-DELIVER-REPORT unavailable
Updated•11 years ago
|
Component: DOM: Device Interfaces → RIL
Product: Core → Boot2Gecko
Target Milestone: mozilla26 → ---
Reporter | ||
Comment 14•11 years ago
|
||
Set status to Reopened.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 15•11 years ago
|
||
Why reopening this? This one has been solved.
Reporter | ||
Comment 16•11 years ago
|
||
The build I filed the bug with is wasabi which is CDMA, it's still no fixed yet.
Summary: B2G SMS: regression in bug 899885 made SMS-DELIVER-REPORT unavailable → [wasabi] B2G SMS: regression in bug 899885 made SMS-DELIVER-REPORT unavailable
Comment 17•11 years ago
|
||
(In reply to Enpei from comment #16)
> The build I filed the bug with is wasabi which is CDMA, it's still no fixed
> yet.
Please track bug 913313 instead. We didn't noticed this is for CDMA, and we had same problem for GSM and had been fixed in this bug.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Summary: [wasabi] B2G SMS: regression in bug 899885 made SMS-DELIVER-REPORT unavailable → B2G SMS: regression in bug 899885 made SMS-DELIVER-REPORT unavailable
Reporter | ||
Comment 18•11 years ago
|
||
Sorry, I mixed up this with bug 913313, I will track it there.
Updated•11 years ago
|
blocking-b2g: koi? → koi+
Updated•11 years ago
|
status-firefox26:
--- → fixed
Target Milestone: --- → 1.2 FC (16sep)
You need to log in
before you can comment on or make changes to this bug.
Description
•