search

trigger-corp / browser-extensions

Build and run cross-platform browser extensions from one codebase.
Other
312 stars 52 forks source link

Packaged extensions cannot be installed #3

Open johniw opened 10 years ago

johniw commented 10 years ago

I followed the instructions and setup the environment successfully. After that I created an extension folder and created a new / blank extension. The build and package steps complete successfully but neither the CRX file (which is packaged via Chrome) nor the XPI file can be installed (images attached)

image

image

This is a link to the generated XPI file - https://dl.dropboxusercontent.com/u/9269606/App2.xpi

This is a RAR file to the CRX and PEM files for chrome - https://dl.dropboxusercontent.com/u/9269606/App.rar

I'm running Chrome 29.0.1547.66 m and Firefox 23.0.1

Builds are being generated on Ubuntu 12.04

jaredsohn commented 10 years ago

I had a similar problem when creating a Firefox XPI, but in my case it was likely because I was still using Chrome-specific code. Also Issue #5 suggests a solution for this problem.

On the Chrome side, you should be able to at least debug a bit by looking at the manifest file (manifest.json after building for Chrome). Not all extensions will show buttons; it only does so if the manifest includes a browser_action section (and I think this can be driven by setting up your OpenForge config in the appropriate way.)