Closed Bug 907629 Opened 11 years ago Closed 11 years ago

[Settings][STK] STK menu keeps coming back

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect)

ARM
Gonk (Firefox OS)
defect
Not set
major

Tracking

(b2g-v1.2 fixed)

RESOLVED FIXED
Tracking Status
b2g-v1.2 --- fixed

People

(Reporter: gerard-majax, Unassigned)

Details

(Whiteboard: [u=commsapps-user c=stk p=0])

Attachments

(2 files)

If the user kills the Settings app, STK might come back.

STR:
 0. Receive a call
 1. Hang up on it
 2. STK menu should popup to propose things like "send a message", etc (it does on Orange F SIM card)
 3. Kill the Settings app, like a user would do (via task switcher)

Actual result:
 STK comes back, at the same menu it was.

This is kind of very bothering.
blocking-b2g: --- → koi?
Please note that you might have to reboot the phone as a precondition: for subsequent calls, the STK menu does not pop.
Probably, when you close settings you tell the STK app "STK_RESULT_NO_RESPONSE_FROM_USER" so STK resends the message again until a valid response (for the app) is received

@see https://github.com/mozilla-b2g/gaia/blob/master/apps/settings/js/icc.js#L53

Please, got some traces (with gaia ones enabled) to verify this.
(In reply to Fernando R. Sela (no CC, needinfo please) [:frsela] from comment #2)
> Probably, when you close settings you tell the STK app
> "STK_RESULT_NO_RESPONSE_FROM_USER" so STK resends the message again until a
> valid response (for the app) is received
> 
> @see
> https://github.com/mozilla-b2g/gaia/blob/master/apps/settings/js/icc.js#L53
> 
> Please, got some traces (with gaia ones enabled) to verify this.

I'll check with those asap. But as far as I can tell, the code sending this STK_RESULT_NO_RESPONSE_FROM_USER was correctly triggered
Attached file stk.log
Here is the log. First occurrence of STK is triggered because did not took the call. All subsequents are after I killed the Settings app.
Flags: needinfo?(frsela)
Pointer to Github pull-request
Comment on attachment 793461 [details]
Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/11664

Turns out that while discussing about this bug, julien came with the suggestion of using window.onbeforeunload instead of window.onunload. When doing this, I can't reproduce anymore on Inari.
Attachment #793461 - Flags: review?(frsela)
Comment on attachment 793461 [details]
Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/11664

cool, thanks
Attachment #793461 - Flags: review?(frsela) → review+
Not sure if bug 898236 is the same as this one.
Flags: needinfo?(frsela)
(In reply to Fernando R. Sela (no CC, needinfo please) [:frsela] from comment #8)
> Not sure if bug 898236 is the same as this one.

That might.
Whiteboard: [u=commsapps-user c=stk p=0]
Shipped.
blocking-b2g: koi? → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: