Closed
Bug 1182770
Opened 10 years ago
Closed 10 years ago
MMS somtimes gets reported as in error when it has been sent
Categories
(Firefox OS Graveyard :: RIL, defect)
Firefox OS Graveyard
RIL
Tracking
(firefox42 fixed, b2g-v2.2 affected, b2g-v2.2r affected, b2g-master affected)
RESOLVED
FIXED
FxOS-S3 (24Jul)
People
(Reporter: gerard-majax, Assigned: bevis)
References
Details
(Keywords: foxfood, regression, Whiteboard: [bzlite])
Attachments
(4 files)
User-Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
Long standing intermittent issue were MMS cannot be sent until user connects data by hand. It seems we get error even though themms actually gets received
| Reporter | ||
Comment 1•10 years ago
|
||
| Reporter | ||
Comment 2•10 years ago
|
||
| Reporter | ||
Comment 3•10 years ago
|
||
| Reporter | ||
Comment 4•10 years ago
|
||
It looks like I mostly reproduce this when I'm under LTE coverage.
Summary: unable to send MMS → MMS somtimes gets reported as in error when it has been sent
| Reporter | ||
Updated•10 years ago
|
Component: Gaia::Feedback → RIL
| Reporter | ||
Updated•10 years ago
|
Comment 5•10 years ago
|
||
Hey Bevis,
Do you have enough information with these logs ?
Flags: needinfo?(btseng)
| Assignee | ||
Comment 6•10 years ago
|
||
Thanks for the log,(In reply to Julien Wajsberg [:julienw] from comment #5)
> Hey Bevis,
>
> Do you have enough information with these logs ?
Thanks for the log.
After investigating the log,
I found a regression of bug 992772 that cause the MmsService sent the request to the network even DNS query was failed. (An abuse of promise that was unexpectedly fulfilled after rejected [1])
I'll take this bug to follow up.
Hi Lissy,
In addition to the regression I found,
there is one more problem about why the DNS query is failed.
Is it possible to capture the tcpdump and the adb logcat with ril/mms/network debug flags enabled for further clarification or Is there any QA in France who is able to help on this?
https://github.com/bevis-tseng/Debug_Tools
Thanks!
[1] https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/annotate/8d59402ba85a/dom/mobilemessage/gonk/MmsService.js#l733
Assignee: nobody → btseng
Blocks: 992772
status-b2g-v2.2:
--- → affected
status-b2g-v2.2r:
--- → affected
status-b2g-master:
--- → affected
Flags: needinfo?(btseng) → needinfo?(lissyx+mozillians)
Keywords: regression
| Reporter | ||
Comment 7•10 years ago
|
||
No it's not. I don't reproduce that often and when I do I cannot get tcpdump often. Besides, I did enable RIL, Network AND MMS in the logs I shared.
Flags: needinfo?(lissyx+mozillians)
| Assignee | ||
Comment 8•10 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #7)
> No it's not. I don't reproduce that often and when I do I cannot get tcpdump
> often. Besides, I did enable RIL, Network AND MMS in the logs I shared.
Never mind.
I'll fix the regression I found firstly to fix the wrong identification of the mms transaction result between sender and receiver.
| Reporter | ||
Comment 9•10 years ago
|
||
Maybe you can split through more debug for the DNS issue, so that we can have a clue next time it happens with just the device logs.
| Assignee | ||
Comment 10•10 years ago
|
||
Hi Edgar,
May I have your review for this fix?
Thanks!
Attachment #8634591 -
Flags: review?(echen)
Comment 11•10 years ago
|
||
Comment on attachment 8634591 [details] [diff] [review]
(v1) Patch Catch Rejected Promise Properly when Failed to ensure routing.
Review of attachment 8634591 [details] [diff] [review]:
-----------------------------------------------------------------
Looks good to me, thank you.
Attachment #8634591 -
Flags: review?(echen) → review+
| Assignee | ||
Comment 12•10 years ago
|
||
update try server result:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=4fd6bd3209c6
Keywords: checkin-needed
Comment 13•10 years ago
|
||
Keywords: checkin-needed
Comment 14•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox42:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → FxOS-S3 (24Jul)
You need to log in
before you can comment on or make changes to this bug.
Description
•