Closed
Bug 961975
Opened 12 years ago
Closed 12 years ago
Cost control app are unable to start on Tarako
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: dwi2, Unassigned)
Details
This only happens on Tarako with nuwa being enabled.
Version:
Gaia 779ac172a144c0d204abdb696ca083144d6f0f3b
BuildID 20140121112325
Version 28.0a2
ro.build.version.incremental=28
ro.build.date=Tue Jan 21 11:22:32 CST 2014
STR:
1. Boot up Tarako without any SIM inserted
2. Start Usage app
Actual Result:
Blank app screen
Expected Result:
Screen should display "No SIM inserted \n Insert a SIM to enable Usage"
I saw these JavaScript Errors in the log
E/GeckoConsole( 764): [JavaScript Error: "this._browserElementChild.showModalPrompt is not a function" {file: "resource://gre/modules/BrowserElementPromptService.jsm" line: 36}]
E/GeckoConsole( 764): [JavaScript Error: "NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS: '[JavaScript Error: "this._browserElementChild.showModalPrompt is not a function" {file: "resource://gre/modules/BrowserElementPromptService.jsm" line: 36}]' when calling method: [nsIPrompt::alert]" {file: "app://costcontrol.gaiamobile.org/js/common.js" line: 306}]
| Reporter | ||
Updated•12 years ago
|
Whiteboard: [tarako]
| Reporter | ||
Comment 1•12 years ago
|
||
These error happens when Gaia invoke 'window.alert'.
flows:
costcontrol/js/app.js#init() -> checkSIMStatus() -> checkCardState() -> showSimErrorDialog() -> costcontrol/js/common.js#modalAlert() -> window.alert()
I also tried the Gecko patch in 960641 but this error still exists.
Hi Patrick,
Do you have time to take a look at this on Gecko side? thanks
Flags: needinfo?(pwang)
Comment 2•12 years ago
|
||
(In reply to Tzu-Lin Huang [:dwi2] from comment #1)
> Do you have time to take a look at this on Gecko side? thanks
Well, it seems that the BEC is not registered to the prompt service correctly. I can take a look.
Flags: needinfo?(pwang)
Comment 3•12 years ago
|
||
The daily build includes the WIP of bug 941466, and the patch is not ready to use (and still fail to pass automation test).
Comment 4•12 years ago
|
||
Let's close this bug since the patch which makes this failure is not in our code base.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•