Closed
Bug 1132007
Opened 10 years ago
Closed 10 years ago
Initialise _iccChannelCalback in RilContentHelper.js
Categories
(Firefox OS Graveyard :: RIL, defect)
Tracking
(blocking-b2g:2.2+, firefox36 wontfix, firefox37 wontfix, firefox38 fixed, b2g-v2.2 fixed, b2g-master fixed)
People
(Reporter: tauzen, Assigned: tauzen)
References
Details
Attachments
(1 file, 1 obsolete file)
(deleted),
patch
|
tauzen
:
review+
bajaj
:
approval-mozilla-b2g37+
|
Details | Diff | Splinter Review |
While running SecureElement code (Bug 879861) on master I've got "this._iccChannelCallback is undefined" error. _iccChannelCallback was introduced in Bug 1081789, and the original version of the patch actually initialised it. The initialisation line was probably lost while rebasing to master. It needs to be added back for SE API to work properly.
Assignee | ||
Updated•10 years ago
|
Assignee | ||
Comment 1•10 years ago
|
||
Hi Edgar, since you reviewed the patches in Bug 1081789 could you take a look a this? From my perspective this looks like a regression caused by rebase.
Attachment #8562758 -
Flags: review?(echen)
Updated•10 years ago
|
Assignee: nobody → kmioduszewski
Comment 3•10 years ago
|
||
Comment on attachment 8562758 [details] [diff] [review]
0001-Bug-1132007-Initialise-_iccChannelCalback-in-RilCont.patch
Review of attachment 8562758 [details] [diff] [review]:
-----------------------------------------------------------------
r=me with comment addressed. Thank you, kmioduszewski!
Please also help to add `_iccChannelCallback: null` right before `_addIccChannelCallback: function(requestId, channelCb) {` [1], just like what |_iccListeners| does [2].
[1] https://dxr.mozilla.org/mozilla-central/source/dom/system/gonk/RILContentHelper.js#596
[2] https://dxr.mozilla.org/mozilla-central/source/dom/system/gonk/RILContentHelper.js#561
Attachment #8562758 -
Flags: review?(echen) → review+
Assignee | ||
Comment 4•10 years ago
|
||
Thanks Edgar! I've updated the patch as you requested. Once I'll get a green try build I'll request checkin.
Attachment #8562758 -
Attachment is obsolete: true
Attachment #8563340 -
Flags: review+
Assignee | ||
Comment 5•10 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=171f0e2fdaa2
I think there's a global problem with OSX builds, apart from that everything seems to be ok.
Keywords: checkin-needed
Comment 6•10 years ago
|
||
Keywords: checkin-needed
Comment 7•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox38:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 2.2 S6 (20feb)
Assignee | ||
Comment 8•10 years ago
|
||
Comment on attachment 8563340 [details] [diff] [review]
(v1.1) 0001-Bug-1132007-Initialise-_iccChannelCalback-in-RilCont.patch
NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.
[Approval Request Comment]
Bug caused by (feature/regressing bug #):
Bug 1132007, see more details in comment 0
User impact if declined:
Broken Secure Element API feature - Bug 879861
Testing completed: on device testing complete
Risk to taking this patch (and alternatives if risky): none
String or UUID changes made by this patch: none
Attachment #8563340 -
Flags: approval-mozilla-b2g37?
Updated•10 years ago
|
Attachment #8563340 -
Flags: approval-mozilla-b2g37? → approval-mozilla-b2g37+
Comment 9•10 years ago
|
||
status-b2g-v2.2:
--- → fixed
status-b2g-master:
--- → fixed
status-firefox36:
--- → wontfix
status-firefox37:
--- → wontfix
You need to log in
before you can comment on or make changes to this bug.
Description
•