Closed Bug 988621 Opened 11 years ago Closed 11 years ago

TypeError: IccHelper.iccInfo is null

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:1.3+, b2g-v1.3 fixed, b2g-v1.3T fixed, b2g-v1.4 unaffected, b2g-v2.0 unaffected)

RESOLVED FIXED
blocking-b2g 1.3+
Tracking Status
b2g-v1.3 --- fixed
b2g-v1.3T --- fixed
b2g-v1.4 --- unaffected
b2g-v2.0 --- unaffected

People

(Reporter: anshulj, Assigned: arthurcc)

References

Details

Attachments

(1 file)

I am seeing the following error intermittently after reboot and consistently during our internal marionette test scripts. TypeError: IccHelper.iccInfo is null at: app://system.gaiamobile.org/js/call_forwarding.js line: 85 We need a if (IccHelper.iccInfo && IccHelper.iccInfo.iccid) check around block of code on line 85 as done in other JS files that use iccid. Please see bug 914673 as as reference.
Adding a check looks good to me. However, I was curious about why there is no iccInfo when cfstatechange. Are the tests being done using a dual sim device? There is no dual sim support for call forwarding in v1.3.
(In reply to Arthur Chen [:arthurcc] from comment #1) > Adding a check looks good to me. However, I was curious about why there is > no iccInfo when cfstatechange. I tried to debug that but the issue happens randomly so I couldn't get very far with my debugging session. > Are the tests being done using a dual sim > device? There is no dual sim support for call forwarding in v1.3. Single SIM.
Inder, Can we please help understand if 1.3 or 1.4 is a higher priority?
Flags: needinfo?(ikumar)
:Preeti -- this is a good to have things and as per my understanding is a 2 line fix to do the null check so shouldn't be difficult to get it fixed. But, if there is a resource conflict then 1.4 issues are higher priority than this particular issue. Currently, as a workaround we have put in a temporary fix in our build.
Flags: needinfo?(ikumar)
See Also: → 989022
Status: NEW → ASSIGNED
Component: Gaia::Settings → Gaia::System
Assignee: nobody → arthur.chen
Alive, could you help review the simple patch?
Attachment #8398410 - Flags: review?(alive)
Tim, can you do the blocking triage here?
Flags: needinfo?(timdream)
Attachment #8398410 - Flags: review?(alive) → review+
blocking-b2g: 1.3? → 1.3+
Flags: needinfo?(timdream)
Comment on attachment 8398410 [details] link to https://github.com/mozilla-b2g/gaia/pull/17747 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 #): Unknown gecko issue [User impact] if declined: No big impact to users but we will see javascript errors in the console. [Testing completed]: N/A [Risk to taking this patch] (and alternatives if risky): Pretty low as the patch simply adds a null check. [String changes made]: N/A
Attachment #8398410 - Flags: approval-gaia-v1.3?(fabrice)
By [Testing completed]: N/A, I meant manual testing completed.
Comment on attachment 8398410 [details] link to https://github.com/mozilla-b2g/gaia/pull/17747 Stealing since Fabrice is out.
Attachment #8398410 - Flags: approval-gaia-v1.3?(fabrice) → approval-gaia-v1.3+
v1.3: 24f562fce468fc948ac9e6185e002c23350cb9ee
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
So we aren't landing this on v1.4/v1.5?
status-b2g-v1.4: --- → ?
status-b2g-v2.0: --- → ?
Flags: needinfo?(arthur.chen)
There are already null checks in both branches.
Flags: needinfo?(arthur.chen)
Flags: in-moztrap-
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: