I am building a firefox addon for the first time.
When I try to install I keep getting this error message "Addon not compatible with firefox 4.0"
I tried to install on older version of firefox also but no luck. I am not sure what i am doing wrong. Here is my install.rdf file.
<Description about="urn:mozilla:install-manifest">
<em:id>priyank#techstudio.in</em:id>
<em:name>Chrome Dictionary</em:name>
<em:version>0.1</em:version>
<em:type>2</em:type>
<em:creator>Priyank Gandhi</em:creator>
<em:description>A sample extension.</em:description>
<em:homepageURL>http://www.priyankgandhi.com/</em:homepageURL>
<!-- Mozilla Firefox -->
<em:targetApplication>
<Description>
<em:id>{ac236786-4ca7-48d0-8f3b-034fe9ad2dbc}</em:id>
<em:minVersion>3.0</em:minVersion>
<em:maxVersion>6.0.*</em:maxVersion>
</Description>
</em:targetApplication>
</Description>
Here is the structure of my files:
|-chrome.manifest
|-install.rdf
|-chrome
|mydir
||content
||-main.xul
||-main.js
||skin
||-main.css
Thanks
I think your target application em:id is off:
{ec8030f7-c20a-464f-9b0e-13a3a9e97384} - Firefox's application ID.
Source: https://developer.mozilla.org/en/Building_an_Extension
Related
First of all let me say that we are pretty new with this "windows app" developing process.
Our customers want us to develop an app working as click to call. The app is working just fine, but we are encountering problems with that appearing in the "default apps for protocol" menus for callto and tel protocols.
We are kinda clueless about the steps needed to achieve this goal.
What we tried:
Adding the following to the manifests files.
<Applications>
<Application Id="App" StartPage="default.html">
<Extensions>
<Extension Category="windows.protocol">
<Protocol Name="alsdk" />
</Extension>
</Extensions>
</Application>
</Applications>
Modifying the registry keys:
[HKEY_CLASSES_ROOT\tel]
#="URL:custom_app"
"URL Protocol"=""
[HKEY_CLASSES_ROOT\tel\shell]
[HKEY_CLASSES_ROOT\tel\shell\open]
[HKEY_CLASSES_ROOT\tel\shell\open\command]
#="<path_to_exe>.app.exe" "%1"
Any help WILL be appreciated. Thanks in advance.
Solved by registering the app first and then creating all the needed associations.
Windows Registry Editor Version 5.00
;Register The App
[HKEY_LOCAL_MACHINE\SOFTWARE\RegisteredApplications]
"CustomApp"="Software\\Clients\\CustomApp\\Capabilities"
[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\CustomApp]
#="CustomApp"
[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\CustomApp\Capabilities\StartMenu]
"CustomApp"="CustomApp"
[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\CustomApp\Capabilities\UrlAssociations]
"callto"="CustomApp.callto"
"tel"="CustomApp.tel"
[HKEY_CLASSES_ROOT\CustomApp.callto]
#="CustomApp callto Handler"
[HKEY_CLASSES_ROOT\CustomApp.callto\shell\open\command]
#="\"<path_to_app>\\CustomApp.exe\" \"%1\""
[HKEY_CLASSES_ROOT\CustomApp.tel]
#="CustomApp tel Handler"
[HKEY_CLASSES_ROOT\CustomApp.tel\shell\open\command]
#="\"<path_to_app>\\CustomApp.exe\" \"%1\""
If you have any file associations, you can add them easily doing this:
[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\CustomApp\Capabilities\FileAssociations]
".foo"="CustomApp.foo"
[HKEY_CLASSES_ROOT\CustomApp.foo]
#="CustomApp foo Handler"
[HKEY_CLASSES_ROOT\CustomApp.foo\shell\open\command]
#="\"<path_to_app>\\CustomApp.exe\" \"%1\""
In JMeter, use Templates > Recording
Unfold Workbench > HTTP(S) Test Script Recorder and start recorder
A certificate authority file is generated in jmeter/bin folder called ApacheJMeterTemporaryRootCA.crt
Install it in Android
Connected my device in to desktop by advance setting in wifi
But its not recording my action in desktop.............
How to find whether my device is connected but desktop?
First use JMeter Recording Template
Then start JMeter's HTTP(S) Test Script Recorder, it will generate in jmeter/bin folder, a file called ApacheJMeterTemporaryRootCA.crt .
Copy file to your android device and install it as CA Certificate.
See How do I install a user certificate? thread for more details.
The certificate has limited life time (defaults to 7 days) but you can extend it by setting in user.properties
proxy.cert.validity=Number of days
Now the problem you'll face in Android >= 7.0 is that applications only use by default System installed Certificates.
So you'll need to ask developper of application to modify the APK, see why here.
Edit manifest and add :
android:networkSecurityConfig="#xml/network_security_config"
You'll get:
<?xml version="1.0" encoding="utf-8"?>
<manifest ... >
<application android:networkSecurityConfig="#xml/network_security_config"
... >
...
</application>
</manifest>
Then add in res/xml/network_security_config.xml this:
<?xml version="1.0" encoding="utf-8"?>
<network-security-config>
<base-config>
<trust-anchors>
<!-- Trust preinstalled CAs -->
<certificates src="system" />
<!-- Additionally trust user added CAs -->
<certificates src="user" />
</trust-anchors>
</base-config>
</network-security-config>
Note that this is needed whatever tool you use (Neoload, LoadRunner, ...)
For full details read:
https://www.ubik-ingenierie.com/blog/how-to-record-android-application-using-https-traffic-jmeter/
Is there a way to work on Firefox with selenium 3.4 as
I am always getting error as below:-
"FirefoxDriver cannot be resolved to a type"
WebDriver will support the latest firefox also. but you have to set the properties for that
download "geckodriver.exe" file and download the file from below URL :-
https://github.com/mozilla/geckodriver/releases
System.setProperty("webdriver.gecko.driver","E:\\SeleniumAutomation\\geckodriver-v0.9.0-win64\\geckodriver.exe");
WebDriver driver = new FirefoxDriver();
driver.get("http://stackoverflow.com/");
Update your firefox and selenium server and client-combined jar
I am trying to make an installer with izpack 4.3.5. While installing, a shortcut should be added to the users Desktop. Though I have added the ShortcutPanel and did not add the skipOnNotSupported no panel is shown and no shortcut is created though it complies successfully.
I already took a look at the following post (izpack: create shortcut on windows) but couldn't figure out my mistake.
Here is part of my install-file:
<panels>
<panel classname="TargetPanel"/>
<panel classname="PacksPanel"/>
<panel classname="ShortcutPanel"/>
<panel classname="InstallPanel"/>
<panel classname="SimpleFinishPanel"/>
</panels>
<packs>
...
</packs>
<resources>
<res src="shortcut.xml" id="shortcut.xml"/>
</resources>
<natives>
<native type="izpack" name="ShellLink.dll"/>
<native type="izpack" name="ShellLink_x64.dll"/>
</natives>
And here is my shortcut XML:
<izpack:shortcuts version="5.0"
xmlns:izpack="http://izpack.org/schema/shortcuts"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://izpack.org/schema/shortcuts http://izpack.org/schema/5.0/izpack-shortcuts-5.0.xsd">
<shortcut
name = "test"
target = "$INSTALL_PATH\test.jar"
description="test"
programGroup="true"
desktop="yes"
applications="yes"
startMenu="yes"/>
<lateShortcutInstall />
</izpack:shortcuts>
Any ideas?
UPDATE:
I also tried to remove the lateShortcutInstall, but nothing changed.
Thanks in advance
You are trying to make install files for izPack version 5 work with izPack 4.3.5 (notice the version="5.0" in the shortcut XML?). This will not work as the format has changed in subtle details.
I suggest that you move to a current izPack 5 version (5.1.0 has just been released). It is actively maintained, more stable and better documented than 4.3.5.
If you are stuck on 4.3.5 please read my other post here: izpack-maven-plugin is not including native libraries by default and remove the <natives> element.
My Firefox extension is not hosted on the official extension site. It is hosted on a secure (https) server. From what I have read, I do not need to sign my add-on, right?
The problem is that it is not working. I install my plugin, and click on 'Check for updates', but it says no updates have been found. I have set the version in the update manifest and in the install manifest from initial.rev332 to initial.rev333.
Could someone shed some light on my situation? Thanks very much :)
My install manifest...
<?xml version="1.0" encoding="utf-8"?>
<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:em="http://www.mozilla.org/2004/em-rdf#">
<Description about="urn:mozilla:install-manifest">
<em:id>jid0-BsYlcooDmgR331LCKZwABfD4yQk#jetpack</em:id>
<em:version>initial.rev333</em:version>
<em:type>2</em:type>
<em:bootstrap>true</em:bootstrap>
<em:unpack>false</em:unpack>
<!-- Firefox -->
<em:targetApplication>
<Description>
<em:id>{jid0-BsYlcooDmgR331LCKZwABfD4yQk#jetpack}</em:id>
<em:minVersion>3.4</em:minVersion>
<em:maxVersion>30.*</em:maxVersion>
</Description>
</em:targetApplication>
<!-- Front End MetaData -->
<em:name>iStyla</em:name>
<em:description>iStyla is a marketplace for themes for Facebook, Twitter and Google+ </em:description>
<em:creator>iStyla</em:creator>
<em:homepageURL>https://www.istyla.com/</em:homepageURL>
<em:updateURL>https://www.istyla.com/Updates/firefox.rdf</em:updateURL>
</Description>
</RDF>
My Update Manifest
<?xml version="1.0"?>
<r:RDF xmlns:r="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns="http://www.mozilla.org/2004/em-rdf#">
<r:Description about="urn:mozilla:extension:jid0-BsYlcooDmgR331LCKZwABfD4yQk#jetpack">
<updates>
<r:Seq>
<r:li>
<r:Description>
<version>initial.rev333</version>
<targetApplication>
<r:Description>
<id>{jid0-BsYlcooDmgR331LCKZwABfD4yQk#jetpack}</id>
<minVersion>3.0</minVersion>
<maxVersion>30.*</maxVersion>
<updateLink>https://www.istyla.com/Updates/Firefox.xpi</updateLink>
<updateHash>
sha256:af031d8bb9303a42ab1f270845e9c692d65cd4fc
</updateHash>
</r:Description>
</targetApplication>
</r:Description>
</r:li>
</r:Seq>
</updates>
</r:Description>
</r:RDF>
I think your addon version number needs to be in a different format: https://developer.mozilla.org/en/Install_Manifests#version
Try the versioning format listed here to differentiate versions: https://developer.mozilla.org/en/Toolkit_version_format
Maybe try <em:version>0.0.333</em:version>
Also, I don't think <em:maxVersion>30.*</em:maxVersion> is valid (I could be wrong though. If you're not hosting it on AMO it might work alright). Here is the list of valid Firefox version numbers available FWIW: https://addons.mozilla.org/en-US/firefox/pages/appversions/