[1.OS Version ]: v1.3t v1.4 [2.Network ]: GSM [3.SIM Card ]: SIM1:-Aircel [4.Testing Steps ]: a) Make a call or send a message from DUT . b) DUT again & again shows message "Session Expired" with Aircel operator. [5.Testing Result ]:Firefox shows a message "session expired" again and again. [6.Expected Result ]: Firefox should not show that type of message [7.Place ]: India

I checked the code and found ffos shows "Session Expired" when receive a blank USSD message. Here is the main log for 7715 v1.4 Please help to check why ffos shows "Session Expired" so much.

Here is a radio log for sprd7715 v1.4 Hi Evelyn Please help to check this bug. Thanks.

Hi Etienne, do you have any hint about this issue? I can't find where the message comes from after a grep in codes. :(

(In reply to Evelyn Hung [:evelyn] from comment #3) > Hi Etienne, do you have any hint about this issue? I can't find where the > message comes from after a grep in codes. :( Comment 1 is probably correct [1], but I don't know why we're receiving a ussd-received system message here. [1] https://github.com/mozilla-b2g/gaia/blob/master/apps/communications/dialer/js/mmi_ui.js#L173-175

(In reply to Etienne Segonzac (:etienne) from comment #4) > (In reply to Evelyn Hung [:evelyn] from comment #3) > > Hi Etienne, do you have any hint about this issue? I can't find where the > > message comes from after a grep in codes. :( > > Comment 1 is probably correct [1], but I don't know why we're receiving a > ussd-received system message here. > > > [1] > https://github.com/mozilla-b2g/gaia/blob/master/apps/communications/dialer/ > js/mmi_ui.js#L173-175 Hi Etienne I think it is the b2g received blank ussd messages that lead to this appearance. Is there any method to avoid receiving blank ussd message or don't show the blank ussd message on screen? Thanks.

Hi Etienne Can this patch be accepted to avoid this? Thanks.

I'd like to understand what's happening before reviewing anything. Why are we receiving this empty ussd?

(In reply to Etienne Segonzac (:etienne) from comment #7) > I'd like to understand what's happening before reviewing anything. Why are > we receiving this empty ussd? The empty ussd messages were received from network. Our colleague who is responsible for the modem module said that android also received this empty ussd message after analyzing the android log, but android showed nothing on the screen. So I wonder if ffos can also not show this message. Thanks.

(In reply to wei.gao from comment #8) > (In reply to Etienne Segonzac (:etienne) from comment #7) > > I'd like to understand what's happening before reviewing anything. Why are > > we receiving this empty ussd? > > The empty ussd messages were received from network. > > Our colleague who is responsible for the modem module said that android also > received this empty ussd message after analyzing the android log, but > android showed nothing on the screen. > > So I wonder if ffos can also not show this message. > Hey ferjm, I know you didn't touch this in a while, but since you did gecko and gaia work on this I think you are the best person to ask. Is it safe to just ignore those empty ussd messages? Or will we be discarding important things like the session ending.

I think that we can ignore the empty ussd messages if we have another way to tell the user that the session is expired (we have a flag for that [1]). Maybe disabling the MMI screen if it is being shown or directly closing it. I have a vague memory about this being a certification blocker. Beatriz, can you confirm this please? [1] https://mxr.mozilla.org/mozilla-central/source/dom/webidl/USSDReceivedEvent.webidl#18

Yes it is a certification requirement, the USSD session expiration must be shown to the user when the network closes it.

Gabriele, I think this is fixed in whatever bug we started ignoring blank USSD messages in. Could you please either dup this bug to that one, or resolve this if you can't find it?

(In reply to Doug Sherk (:drs) (use needinfo?) from comment #12) > Gabriele, I think this is fixed in whatever bug we started ignoring blank > USSD messages in. Could you please either dup this bug to that one, or > resolve this if you can't find it? Hi Gabriele This issue doesn't happen again. So we can close this bug. Thanks.

This is most likely a duplicate of bug 1057455 so I'm dup'ing against that one.