Closed
Bug 1034279
Opened 10 years ago
Closed 10 years ago
USSD messages not displayed if user leaves Dialer while sending
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Firefox OS Graveyard
Gaia::Dialer
Tracking
(blocking-b2g:1.4+, b2g-v1.4 fixed, b2g-v2.0 verified, b2g-v2.0M verified, b2g-v2.1 verified)
People
(Reporter: rik, Assigned: rik)
References
Details
Attachments
(4 files, 1 obsolete file)
46 bytes,
text/x-github-pull-request
|
etienne
:
review+
|
Details | Review |
3.23 KB,
patch
|
bajaj
:
approval-gaia-v1.4+
|
Details | Diff | Splinter Review |
12.61 KB,
patch
|
bajaj
:
approval-gaia-v2.0+
|
Details | Diff | Splinter Review |
1.59 MB,
video/mp4
|
Details |
STRs:
1) Compose a MMI and call it
2) While the "Sending…" screen is displayed, press the home button
Expected:
Dialer comes to the foreground with the MMI displayed.
Actual:
MMI is displayed but in the background.
Assignee | ||
Comment 1•10 years ago
|
||
I have a patch for this but no tests yets. Will write those tomorrow.
Assignee | ||
Comment 2•10 years ago
|
||
Attachment #8450949 -
Flags: review?(etienne)
Updated•10 years ago
|
Attachment #8450949 -
Flags: review?(etienne) → review+
Assignee | ||
Comment 3•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 6•10 years ago
|
||
Thanks to the report in bug 1063407 we could better ascertain the impact of this issue: we thought it was a corner case but instead it's needed for STK to work properly from the settings app. One of our partners is asking for landing this on v1.4 (see bug 1063407 comment 6). This has been in master for a long time now and it's well tested but I'm not sure if we're still taking uplifts to v1.4. How should we proceed?
status-b2g-v1.4:
--- → affected
status-b2g-v2.0:
--- → affected
status-b2g-v2.0M:
--- → affected
status-b2g-v2.1:
--- → fixed
status-b2g-v2.2:
--- → fixed
Flags: needinfo?(release-mgmt)
Comment 8•10 years ago
|
||
(In reply to Gabriele Svelto [:gsvelto] from comment #6)
> Thanks to the report in bug 1063407 we could better ascertain the impact of
> this issue: we thought it was a corner case but instead it's needed for STK
> to work properly from the settings app. One of our partners is asking for
> landing this on v1.4 (see bug 1063407 comment 6). This has been in master
> for a long time now and it's well tested but I'm not sure if we're still
> taking uplifts to v1.4. How should we proceed?
Given the DUP and the user impact here I'll block this on 1.4. can you please seek the approval for 1.4 and 2.0 to get this landed on those branches ? (filling the form once should be enough)
Flags: needinfo?(bbajaj)
Updated•10 years ago
|
blocking-b2g: --- → 1.4+
Comment 9•10 years ago
|
||
This is the cherry-picked patch for v1.4. The only change it required was removing the changes from the mmi_ui_test.js file which was not present in v1.4. The rest of the patch applied cleanly.
[Approval Request Comment]
[Bug caused by] (feature/regressing bug #): bug 1016885
[User impact] if declined: Interaction with the STK in the Settings app is partially broken, see bug 1063407
[Testing completed]: Covered with unit-tests and tested on an affected device, see bug 1063407 comment 5
[Risk to taking this patch] (and alternatives if risky): This patch has been in master for a long time already and proved to work well
[String changes made]: None
Attachment #8486021 -
Flags: approval-gaia-v1.4?(release-mgmt)
Comment 10•10 years ago
|
||
The patch applies cleanly to v2.0, I'm attaching here nonetheless for requesting approval. See comment 9 for the details. The same patch can be applied to v2.0m too though I'm not sure what's the landing policy for that branch.
Attachment #8486028 -
Flags: approval-gaia-v2.0?(release-mgmt)
Comment 11•10 years ago
|
||
2.0m is managed by the devices team, so you needn't worry about it :)
status-b2g-v2.2:
fixed → ---
Target Milestone: --- → 2.0 S6 (18july)
Comment 12•10 years ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #11)
> 2.0m is managed by the devices team, so you needn't worry about it :)
Thanks, good to know :)
Updated•10 years ago
|
Attachment #8486021 -
Flags: approval-gaia-v1.4?(release-mgmt) → approval-gaia-v1.4+
Updated•10 years ago
|
Attachment #8486028 -
Flags: approval-gaia-v2.0?(release-mgmt) → approval-gaia-v2.0+
Comment 13•10 years ago
|
||
Comment 14•10 years ago
|
||
Comment 15•10 years ago
|
||
Verify OK, this issue can't repro on Woodduck 2.0.
Attached: Verify video.MP4
Reproducing rate: 5/5
Woodduck 2.0 Build:
Gaia-Rev 7bc7f75d712ccef535fd371bfcc7fe61dcdcf874
Gecko-Rev 8f21e6d8abf8ee01d8da066495d8febf3138375a
Build-ID 20141113050313
Version 32.0
Comment 16•10 years ago
|
||
Updated•10 years ago
|
Updated•10 years ago
|
Group: woodduck-confidential
Comment 17•10 years ago
|
||
Please don't attach confidential information (in this case the device shown in attachment 8522000 [details]) to a public bug and then make it confidential. This bug has been public since it was opened and needs to remain so in order for people to refer to it when analyzing the related code / commit. Please remove the video and make this bug public again.
Group: woodduck-confidential
Flags: needinfo?(yue.xia)
Updated•10 years ago
|
Group: woodduck-confidential
Updated•10 years ago
|
Attachment #8522000 -
Attachment is obsolete: true
Flags: needinfo?(yue.xia)
Updated•10 years ago
|
Group: woodduck-confidential
Comment 18•10 years ago
|
||
This issue has been verified successfully on Flame v2.1 & v2.0
See attachment: verify_video.MP4
Reproducing rate: 0/5
Flame 2.1 versions:
Gaia-Rev 38e17b0219cbc50a4ad6f51101898f89e513a552
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/8b92c4b8f59a
Build-ID 20141205001201
Version 34.0
Device-Name flame
FW-Release 4.4.2
FW-Incremental eng.cltbld.20141205.035305
FW-Date Fri Dec 5 03:53:16 EST 2014
Bootloader L1TC00011880
Flame 2.0 versions:
Gaia-Rev 856863962362030174bae4e03d59c3ebbc182473
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/e40fe21e37f1
Build-ID 20141207000206
Version 32.0
Device-Name flame
FW-Release 4.4.2
FW-Incremental eng.cltbld.20141207.034341
FW-Date Sun Dec 7 03:43:52 EST 2014
Bootloader L1TC00011880
You need to log in
before you can comment on or make changes to this bug.
Description
•