I want to publish my extension on Firefox for beta testing team. So someone can express me how to do this.
Or any steps to do them, it will be more help for me.
AMO (addons.mozilla.org) no longer accepts beta versions for listed publication. You can upload your add-on as unlisted which means it can be signed and installed for testing.
Unlisted add-ons will have to be distributed by the developers.
Related
Some OpenTok Developer documentation indicates the Windows SDK v2.16 will support OpenTok communication via web proxy, and that this is currently in Beta. Has anyone on the Beta program seen this work, and is there any indication of when the 2.16 SDK for Windows may be released?
Michael here from the OpenTok team.
We are planning on releasing this feature (IP Proxy) to GA later this month. And we just released SDK 2.17.
I'm compiling Firefox 44.0.2 on my Windows machine using the official guidance: Simple Firefox build. I want to integrate some custom add-ons to my build. The add-ons are usually .xpi files.
How to do this?
The documented way to do this is to include the .xpi file with the distribution in the directory:
[Firefox install directory]/distribution/extensions
The add-on will then be installed in (copied to) each profile upon the first use of that version of Firefox with the profile. The copy of the extension in each profile will be automatically updated using the normal auto-updating procedure. Effectively, the add-on will be treated as if separately installed in each profile. The user will not be asked to confirm installation of the add-on.
For more information see:
Customizing Firefox: Including extensions with your distribution of Firefox (MDN documentation)
Installing extensions (MDN documentation)
Auto update of bundled Firefox extensions (Stackoverflow question)
Install WebExtensions on Firefox from the command line (Stackoverflow question)
This answer was copied from my answer to Integrating an add-on into a custom Firefox build.
I just finished building my first addon for Firefox using the new Addon SDK.
I'm able to download and install the addon on my desktop Firefox 33.0 and it runs without a problem, however when I try to install the same addon on Firefox for Android 33.0 I get an error message: "... could not be installed because it is not compatible with Firefox 33.0"
Do I need to do anything special to allow my addon to run on Firefox for Android? The addon is generic and there's no reason why it shouldn't run on Android
EDIT: It seems like the problem was indeed that some APIs are not supported in Firefox for Android, the link provided by willma contains all the information required to release an addon for mobile.
It is likely you're using a module that isn't compatible with mobile. See the mobile module compatibility list for more details.
We are working on an app for a large customer that can only give us a p12 certificate and a provisioning profile (for security reasons), and no access to iTunes Connect or their developer center.
Is it possible to make a build signed with this provisoning profile with the latest Xamarin Studio and XCode 5.0.2?
I have been able to do so thus far on our standard account without logging into a developer account in the menu in Xamarin Studio->Preferences->Developer Accounts and doing the same in XCode. Is this a requirement now?
I am a Xamarin Customer Support Engineer.
This is apparently a known issue in Xamarin Studio 4.2.0 and 4.2.1. This is fixed in 4.2.2 should be released very shortly. In the meantime, you can downgrade to 4.0.13 from your account downloads page.
I have an custom addon developed for our workplace (using the add-on SDK) that was originally developed for FF4.
When FF5 came out all I had to do was rebuild the XPI. FF6 was able to use the same XPI.
Now I'm trying to get it running in FF7, and it's not working. I get a "this add-on is not compatible with Firefox 7" when trying to install it.
I've read this blog post:
http://blog.mozilla.com/addons/2011/07/19/firefox-7-compat-looking-to-8/
And from what I can tell none of the changes affect my add-on.
Also running this validation test
https://addons.mozilla.org/en-US/developers/addon/validate
Yields no errors or warnings.
Any clue on how to find out what makes FF7 think it incompatible?
You should use the newest version of the Add-on SDK to rebuild your add-on. Right now, the latest version you get offered on the SDK download page is Add-on SDK 1.1, released on September 13th. It will mark add-ons compatible with everything up to Firefox 8.0a1. You are most likely using an older version, e.g. Add-on SDK 1.0 would only mark add-ons as compatible with Firefox 7.0a1.