Firefox扩展更新下载但无法安装

时间:2013-01-05 05:08:02

标签: firefox-addon firefox-addon-sdk

我在更新我写的Firefox扩展时遇到问题。它似乎下载新版本,卸载旧版本,然后重新安装旧版本。

我使用以下命令打包扩展名:

cfx xpi --update-link=https://www.myextension.com/firefox/myextension.xpi --update-url=https://www.myextension.com/firefox/myextension.update.rdf

我使用about:config属性“extensions.logging.enabled”设置为true运行Firefox并获得以下日志:

*** LOG addons.updates: Requesting https://www.myextension.com/firefox/myextension.update.rdf
*** LOG addons.updates: Found an update entry for myextension@myextension.com version 0.1.1
*** LOG addons.xpi: Download started for https://www.myextension.com/firefox/myextension.xpi to file C:\Users\BENMCC~1\AppData\Local\Temp\tmp-mki.xpi
*** LOG addons.xpi: Download of https://www.myextension.com/firefox/myextension.xpi completed.
*** LOG addons.repository: Requesting https://services.addons.mozilla.org/en-US/firefox/api/1.5/search/guid:myextension%40myextension.com?src=firefox&appOS=WINNT&appVersion=17.0.1
*** LOG addons.xpi: Starting install of https://www.myextension.com/firefox/myextension.xpi
*** LOG addons.xpi: Addon myextension@myextension.com will be installed as a packed xpi
*** LOG addons.xpi: Calling bootstrap method shutdown on myextension@myextension.com version 0.1
*** LOG addons.xpi: Calling bootstrap method uninstall on myextension@myextension.com version 0.1
*** LOG addons.xpi: Loading bootstrap scope from C:\Users\Ben McCann\AppData\Roaming\Mozilla\Firefox\Profiles\pr7jcnq3.default\extensions\myextension@myextension.com.xpi
*** LOG addons.xpi: Calling bootstrap method install on myextension@myextension.com version 0.1
*** LOG addons.xpi: Install of https://www.myextension.com/firefox/myextension.xpi completed.
*** LOG addons.xpi: Calling bootstrap method startup on myextension@myextension.com version 0.1

它将xpi下载到C:\ Users \ BENMCC~1 \ AppData \ Local \ Temp \ tmp-mki.xpi,但随后出现从C:\ Users \ Ben McCann \ AppData \ Roaming \ Mozilla安装旧版本\火狐\ Profiles文件\ pr7jcnq3.default \分机\ myextension@myextension.com.xpi。我检查了后者的xpi,它的版本号错了。

可能会发生什么想法或如何调试问题?

1 个答案:

答案 0 :(得分:1)

事实证明这是因为服务器没有正确设置扩展文件的mime类型。

I submitted a pull request to the Play Framework to fix it.