821663 - [MMI/USSD] USSD is sent in a wrong USSD session if the dialer is killed while an USSD session is opened

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::Dialer, defect, P2)

Description

[Fernando Jiménez Moreno [:ferjm]]

Attachment: Screenshot

STR:

1. Open the dialer app.
2. Dial an USSD code which expects an interactive USSD menu as reply (for ex. *123# with a Vodafone SIM).
3. Once you get the USSD menu, hold the HOME button and kill the dialer app.
4. Reopen the dialer app.
5. The dialer is shown in its keyboard view mode.
6. Send a new USSD code, *123# again, for example.

Expected:

Not sure about the expected behavior, but I would say:

- When the dialer app is reopened, the USSD screen should be shown, instead of the keyboard screen, so the user receives feedback about the active USSD session and is forced to continue with it or manually cancel it by clicking the 'X' button. This is what happen if the app is not killed, but hide.

OR

- When the dialer app is reopened, the previous USSD session is killed so new USSD messages can open each own sessions.

Actual:

The USSD message is sent in the previous session, which is not correct. You can see in the attached screenshot that the Vodafone server is saying "Opción *123# no válida" which means "Not valid *123# option".

Comment 1

[Fernando Jiménez Moreno [:ferjm]]

Nominating as bb+.

If the device ends up in this state, no more USSD messages could be sent until the device is rebooted or the USSD session expires (which might be a really long time with some carriers).

Comment 2

[Fernando Jiménez Moreno [:ferjm]]

Attachment: v1

The patch was built on top of Bug 822577 WIP, so I'll send a PR with the attached patch once Bug 822577 lands.

Comment 3

[Fernando Jiménez Moreno [:ferjm]]

https://github.com/mozilla-b2g/gaia/commit/269a0a22b2e5d03b9b3c1f756661df48859603c1

Comment 4

[David Palomino [:dpalomino]]

This would be a certification blocker, I add the dependency. 

Thks, 
David