653906 - latest sdk source fails cfx run: loader.console is undefined

Status: RESOLVED WORKSFORME

(Add-on SDK Graveyard :: General, defect)

Description

[Dietrich Ayala (:dietrich)]

Using binary at '/Applications/Aurora.app/Contents/MacOS/firefox-bin'.
Using profile at '/Users/dietrich/Library/Application\ Support/Firefox/Profiles/dwgkjdlp.jp-commands'.
TypeError: loader.console is undefined (resource://jid0-ecsieece3xvxl3pxmsnbsskliwc-api-utils-lib/cuddlefish.js:188)
stack:
allowImport([object Object],"resource://jid0-ecsieece3xvxl3pxmsnbsskliwc-api-utils-lib/plain-text-console.js","chrome",null,[object Object])@resource://jid0-ecsieece3xvxl3pxmsnbsskliwc-api-utils-lib/cuddlefish.js:188
syncRequire("chrome")@resource://jid0-ecsieece3xvxl3pxmsnbsskliwc-api-utils-lib/securable-module.js:301
asyncRequire("chrome")@resource://jid0-ecsieece3xvxl3pxmsnbsskliwc-api-utils-lib/securable-module.js:317
@:0

FAIL
Total time: 1.640985 seconds
Program terminated unsuccessfully.

shell returned 255

Comment 1

[Dietrich Ayala (:dietrich)]

creating a new add-on from scratch does not show this error. so it's something in my code, that triggers this error. i updated the source a few days ago, so it's recent (dynamic linker, i'd bet).

if i remove all code in my main.js i see this instead:

TypeError: parent_mi is undefined (resource://jid0-ecsieece3xvxl3pxmsnbsskliwc-api-utils-lib/cuddlefish.js:186)
stack:
allowImport([object Object],"resource://jid0-ecsieece3xvxl3pxmsnbsskliwc-api-utils-lib/plain-text-console.js","chrome",null,[object Object])@resource://jid0-ecsieece3xvxl3pxmsnbsskliwc-api-utils-lib/cuddlefish.js:186
syncRequire("chrome")@resource://jid0-ecsieece3xvxl3pxmsnbsskliwc-api-utils-lib/securable-module.js:301
asyncRequire("chrome")@resource://jid0-ecsieece3xvxl3pxmsnbsskliwc-api-utils-lib/securable-module.js:317
@:0

(also, commenting the code out didn't change anything - we should teach our analyzer to ignore commented-out code. but that's a whole different issue.)

Comment 2

[Dietrich Ayala (:dietrich)]

deleting my key in package.json "fixed" the problem :)

Comment 3

[Brian Warner [:warner :bwarner]]

it certainly does sound like a new-linker problem. Can you paste some of your code? What package.json key did you delete.. the jid?

Comment 4

[Dietrich Ayala (:dietrich)]

yes, deleted the jid.

the add-on is my scratchpad add-on, has tons of different files and miscellaneous cruft in there. i can email to you if you need.

Comment 5

[Brian Warner [:warner :bwarner]]

please do, or gist it, or something. I can't currently imagine why changing the JID would affect this. (modules are looked up in the manifest by URI, which include the JID, but that should get baked into both the manifest and the harness-options.json at the same time, so I don't see how they could mismatch)

Comment 6

[Dietrich Ayala (:dietrich)]

Emailed zip of add-on to Brian.

Comment 7

[Dietrich Ayala (:dietrich)]

Can't reproduce with same data and clean trunk. ->WFM.