1083054 - [Flatfish][System] Can't enter FxOS normally and hang on blue screen when powering on the DUT.

Status: RESOLVED DUPLICATE of bug 941969

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

Description

[eva.chen.fx]

Attachment: issue_PowerOn.jpg

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.124 Safari/537.36

Steps to reproduce:

1. Update a Flatfish to TCP 20141015(https://www.dropbox.com/sh/b2py1btcwstqldl/AAD1u6W3NpgLUyb_rz9-Ytbja/20141015?dl=0)
2. Power on DUT without power core.

Actual: Can not enter Firefox OS normally and hang on blue screen when powering on the tablet.
Expected: The DUT can enter Firefox OS.
See attached: issue_PowerOn.jpg
------------------------------------------------------
* "Broken" Env. Info:
  Device  : Flatfish 2.2 Master
  B2G     : 2.2.0.0-prerelease
  Gaia    : 5f1f0960ae9d22acf2a324ad37a48174d6df87f6
  Gecko   : cb5c7e7246304883b2662cbe5118457b84191f51
  Repro frequency: 100%
  
* "Working" Env. Info:
  Device  : Flatfish 2.2 Master
  B2G     : 2.2.0.0-prerelease
  Gaia    : ba6667c83c5d0fb1e333349dfeaf5f6ca8043e63
  Gecko   : f35a18db764219dce00bd8bffdb93d320dfbf9d7
  BuildID : 20141014014140
  Version : 35.0a1
  Repro frequency: 100%

Comment 1

[YF (Yang)]

adb logcat https://gist.github.com/brion/d30496a1a31223c86875 from tcp irc log.

The appears can see https://github.com/mozilla-b2g/gaia/commit/f6f17b4f4c5aa2e38f82b5c6c449f76974fcb4b1 to fix.

Comment 2

[Brion Vibber]

Note that I can repro this failure with a local build made with PRODUCTION=1, but not with a default build.

Comment 3

[Safwan Rahman (:safwan)]

Hi Raniere,
Can you please branch check this issue and let us know the first bad commit? It will be very much helpful for us.

Comment 5

[YF (Yang)]

I believe this is due to bug 1049439, https://github.com/mozilla-b2g/gaia/commit/c44510bb576ade5edce60c13eb8d18ee2c7a2ed2.

Comment 6

[Safwan Rahman (:safwan)]

George, can you please check the issue which is caused by the patch?

Comment 7

[YF (Yang)]

sorry, I want to withdraw about comment 5 now, I may have been misled.


I see a normal homescreen after try 'adb push' the 'webapps/system.gaiamobile.org/application.zip' (from 20141014 image) to DuT and 'adb reboot'. And seem also normal if just delete these 'gaia_build_' files in the 'webapps/system.gaiamobile.org/application.zip' (20141016) from pull and push.

I see a definite changes in the 'webapps/system.gaiamobile.org/application.zip' file, I did not find where these 'gaia_build_' files appear in gaia changes.

Comment 8

[Noah (NoahSUMO/SolidSnake) [:Noah]]

Hi Fabrice. Thanks for commenting in the other bug.

I realize you are very busy with the Flame bugs but is there anyone you could suggest we reach out to help us fix this bug?

You mentioned you think it's caused by this error:
Very likely caused by this error:
W/GeckoConsole( 1274): [JavaScript Error: "TypeError: invalid 'in' operand this._iccManager" {file: "app://system.gaiamobile.org/gaia_build_defer_index.js" line: 1094}]

That looks like a problem in our code. We'd be very grateful for any developers who could help us fix this bug as this is blocking us from continuing to test FxOS builds on the tablet. Thank you for any help you can provide.

Comment 9

[YF (Yang)]

(In reply to YF (Yang) from comment #7)
> and 'adb reboot'. And seem also normal if just delete these 'gaia_build_'
> files in the 'webapps/system.gaiamobile.org/application.zip' (20141016) from
> pull and push.

Ignore about this, I have an operation missed during attempts.


Seem the window.navigator.mozIccManager is undefined in function icc_init().

I tryed pass the error by coding:
if(typeof this._iccManager !== 'undefined'&&!('STK_RESULT_ACTION_CONTRADICTION_TIMER_STATE'in this._iccManager))

But i got a black homescreen and another error:
[JavaScript Error: "ReferenceError: CallForwarding is not defined" {file: "app://system.gaiamobile.org/gaia_build_defer_index.js" line: 2483}]

Maybe the window.navigator.mozIccManager needs be care.

Comment 10

[[:fabrice] Fabrice Desré]

(In reply to Noah (oldtimer) [:Noah] from comment #8)
> Hi Fabrice. Thanks for commenting in the other bug.
> 
> I realize you are very busy with the Flame bugs but is there anyone you
> could suggest we reach out to help us fix this bug?
> 
> You mentioned you think it's caused by this error:
> Very likely caused by this error:
> W/GeckoConsole( 1274): [JavaScript Error: "TypeError: invalid 'in' operand
> this._iccManager" {file:
> "app://system.gaiamobile.org/gaia_build_defer_index.js" line: 1094}]
> 
> That looks like a problem in our code. We'd be very grateful for any
> developers who could help us fix this bug as this is blocking us from
> continuing to test FxOS builds on the tablet. Thank you for any help you can
> provide.

This error also happens in desktop builds, and they don't start either when building in production mode with NOFTU=1 PRODUCTION=1 make

I get:
JavaScript error: app://system.gaiamobile.org/gaia_build_defer_index.js, line 1095: TypeError: invalid 'in' operand this._iccManager
JavaScript error: app://system.gaiamobile.org/gaia_build_defer_index.js, line 643: ReferenceError: HomescreenWindowManager is not defined
JavaScript error: app://system.gaiamobile.org/gaia_build_defer_index.js, line 637: ReferenceError: AppWindowManager is not defined

Alive, does that ring a bell?

Comment 11

[Sherman Chen [:chens] (inactive)]

Clearing George's ni per comment 7, first bad commit should be https://github.com/mozilla-b2g/gaia/commit/66e26679d4ecd7b1d0a013555e3b33871354046d, see bug 941969 for detail.

Comment 12

[(inactive after 6/18) Alive Kuo [:alive]]

Build system bug, still need George/Ricky's help.

Comment 13

[(Inactive after June) George Duan [:gduan] [:喬智]]

If scripts are merged into one, then we should try to fix original error from each script, or it may probably break entire app.

I tried to do below items with the patch and it works fine with GAIA_OPTIMIZE=1 on b2g-desktop,

1. Change loading order of bootstrap.js and its requiring script , bootstrap.js should put on the bottom. 
2. fix error for call_forwarding.js/icc.js/nfc_handover_manager.js which may have error on device without navigator.mozIccManager , mozMobileConnections ... etc.

I can either provide quick fix in this bug or backout original bug. However, the tree is still closing.