[MMS] No error triggered when sending a MMS fails

RESOLVED WONTFIX

Status

()

Core
DOM: Device Interfaces
RESOLVED WONTFIX
5 years ago
5 years ago

People

(Reporter: gerard, Assigned: michalbe)

Tracking

unspecified
1.1 QE2 (6jun)
ARM
Gonk (Firefox OS)
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
When sending a MMS fails at MMSC level (like, for example, HTTP/403 or HTTP/500 error as in bug 875390), we miss an error poping to notify the user.
(Reporter)

Updated

5 years ago
Summary: No error triggered when sending a MMS fails → [MMS] No error triggered when sending a MMS fails

Updated

5 years ago
blocking-b2g: leo? → leo+
Target Milestone: --- → 1.1 QE2 (6jun)
This feature needs gecko support to have more failing details. 

Chia-hung, 

Would you mind to help us to add these kind of information?? With it, we can show the correct error message to user.
Flags: needinfo?(ctai)
Alexandre, why don't you ask MMS UX owner Ayman first? I think this requested features need UX team's effort. They should the one who decides should we poping to notify the user the error code like 403 or 500. If he say yes, we still need the UX wireframe from him.
Flags: needinfo?(ctai)
Ayman, do you think it is necessary to poping to notify the user when send mms fails at MMSC level? Currently, we will retry sending MMS 3 times, each interval about 5 minutes. After that, the gecko will notify an error to Gaia level. And message bubble in the thread ui will show an error icon.
Flags: needinfo?(aymanmaat)

Comment 4

5 years ago
(In reply to Chia-hung Tai [:ctai :ctai_mozilla :cht] from comment #3)
> Ayman, do you think it is necessary to poping to notify the user when send
> mms fails at MMSC level? Currently, we will retry sending MMS 3 times, each
> interval about 5 minutes. After that, the gecko will notify an error to Gaia
> level. And message bubble in the thread ui will show an error icon.

no it is necessary to have a popup notification informing the user that sending a message has failed for HTTP/403 or HTTP/500. So do not implement such messaging.

We do enough to notify the user that send failure has occurred within the message thread with the presentation of the message bubble in error state and upon tap of error icon the invitation to resend. HTTP/403 or HTTP/500 are not errors like 'flight mode' or 'no sim card'. 'flight mode' or 'no sim card' are errors where the user can actively do something to recover from (turn off flight mode or insert a sim card respectively). The user can do nothing about HTTP/403 or HTTP/500, so it is sufficient to inform them of send failure via the presentation of the message module in error state in the message thread.
Flags: needinfo?(aymanmaat)
Alexandre,
If you want to see the log of MMSC level fail, you can open the MMS log in runtime. Please see bug 868120 for more information.
Error log looks like "xhr error, response headers:XXXXX" or "xhr done, but status = XXXXX".
Do you still need this bug?
Flags: needinfo?(lissyx+mozillians)
Assignee: nobody → mbudzynski
(Reporter)

Comment 6

5 years ago
(In reply to Chia-hung Tai [:ctai :ctai_mozilla :cht] from comment #5)
> Alexandre,
> If you want to see the log of MMSC level fail, you can open the MMS log in
> runtime. Please see bug 868120 for more information.
> Error log looks like "xhr error, response headers:XXXXX" or "xhr done, but
> status = XXXXX".
> Do you still need this bug?

I'm not sure that I correctly understand your question. In my opinion, we should trigger an error if XHR reports an error.
blocking-b2g: leo+ → leo?
Flags: needinfo?(lissyx+mozillians)
Target Milestone: 1.1 QE2 (6jun) → ---
(Reporter)

Comment 7

5 years ago
Sorry for this blocking-b2g revert, I don't know what happened ...
Target Milestone: --- → 1.1 QE2 (6jun)
It is my understanding that this should be closed WONTFIX. We have other bugs to make sure that the "error" icon is displayed to the user (which we of course should).
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX

Updated

5 years ago
blocking-b2g: leo? → ---
status-b2g18: affected → ---
tracking-b2g18: ? → ---
In gecko part, yes, we will handle the error happens and do a retry. Previously there is a bug 877064 about sending retry failure.

(In reply to Alexandre LISSY :gerard-majax from comment #6)
> (In reply to Chia-hung Tai [:ctai :ctai_mozilla :cht] from comment #5)
> > Alexandre,
> > If you want to see the log of MMSC level fail, you can open the MMS log in
> > runtime. Please see bug 868120 for more information.
> > Error log looks like "xhr error, response headers:XXXXX" or "xhr done, but
> > status = XXXXX".
> > Do you still need this bug?
> 
> I'm not sure that I correctly understand your question. In my opinion, we
> should trigger an error if XHR reports an error.
You need to log in before you can comment on or make changes to this bug.