Closed Bug 921958 Opened 11 years ago Closed 11 years ago

B2G RIL: Exception... "'JavaScript component does not have a method named: "notifyCardStateChanged"'

Categories

(Firefox OS Graveyard :: RIL, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:koi+, firefox26 wontfix, firefox27 fixed, b2g-v1.2 fixed, b2g-v1.3 fixed)

RESOLVED FIXED
1.3 Sprint 2 - 10/11
blocking-b2g koi+
Tracking Status
firefox26 --- wontfix
firefox27 --- fixed
b2g-v1.2 --- fixed
b2g-v1.3 --- fixed

People

(Reporter: edgar, Assigned: allstars.chh)

Details

Attachments

(2 files)

09-30 13:42:33.651   108   108 I Gecko   : -*- RILContentHelper: listener for notifyCardStateChanged threw an exception: [Exception... "'JavaScript component does not have a method named: "notifyCardStateChanged"' when calling method: [nsIIccListener::notifyCardStateChanged]"  nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)"  location: "JS frame :: jar:file:///system/b2g/omni.ja!/components/RILContentHelper.js :: _deliverEvent :: line 1846"  data: no]

I got this error in my unagi with below commit information:
* gecko, m-c, 149175:8f805d3ef377
* gaia, master, 64ba02f7bbf70a1877ba9dad6889a17cd25b1d35

I saw this error only when device has just booted up, after that I did not got this error again. Not sure why this exception is thrown.

PS, I have check the behavior of gaia, like settings, lock-screen .. , they work well.
Attached file logcat.txt
Attach logcat
Attachment #811847 - Attachment mime type: text/x-log → text/plain
I also met this error and will check this.
Assignee: nobody → allstars.chh
Comment on attachment 812570 [details] [diff] [review]
Patch

Hi, Fabrice
There is a typo from Bug 893800, see https://bugzilla.mozilla.org/show_bug.cgi?id=893800#c73

Can you help review this for me ?

Thank you
Attachment #812570 - Flags: review?(fabrice)
Attachment #812570 - Flags: review?(fabrice) → review+
https://hg.mozilla.org/mozilla-central/rev/66b79b29c86b
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
This is happening also on 1.2 (detected it on our dogfooding devices). Depending on the order that listeners are called, if the faulty one is called before the other ones, then the device doesn't get any network connectivity (voice or data) and the only way to get out of this state is rebooting the phone and hoping you get lucky.
blocking-b2g: --- → koi?
koi+. please land but watch for failing tests.
blocking-b2g: koi? → koi+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: