Closed Bug 1609221 Opened 5 years ago Closed 5 years ago

TypeError: can't access property "startupData", state is undefined

Categories

(GeckoView :: Extensions, task, P2)

Unspecified
All
task

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1634504

People

(Reporter: agi, Unassigned)

References

(Blocks 1 open bug)

Details

This error is present in the logs of geckoview-junit, it's been happening for a while from what I can see (the wording slightly changed recently).

E GeckoConsole: [JavaScript Error: "TypeError: can't access property "startupData", state is undefined" {file: "resource://gre/modules/addons/XPIProvider.jsm" line: 3011}]

e.g. https://firefoxci.taskcluster-artifacts.net/M6AhJXPvRcW4lvfoJ3HJpA/0/public/test_info//logcat-emulator-5554.log

Summary: TypeError: can't access property "startupData", state is undefined" → TypeError: can't access property "startupData", state is undefined
Blocks: gv-log-spam
No longer blocks: 1609019
Rank: 10
Whiteboard: [geckoview:m76]
Rank: 10 → 25
Whiteboard: [geckoview:m76]

Discussed with robwu, this is caused by our old registerWebExtension API, and it's now gone since our tests use installBuiltIn.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE

This is caused by the use of extensions that have been registered via registerWebExtension, and use the webRequest or proxy API (and previously, also extension messaging, until that changed in bug 1624235).

In Fenix, this bug happens because A-C loads the webcompat add-on in this way.

This bug will only truly be resolved when the deprecated method goes away, so I'm changing the duplicate status to the (open) bug 1634504.

Depends on: 1624235
See Also: → 1601067
You need to log in before you can comment on or make changes to this bug.