Closed
Bug 1201534
Opened 9 years ago
Closed 9 years ago
Installing via direct links to addons XPI fails
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
firefox43 | --- | affected |
People
(Reporter: jonalmeida, Unassigned)
References
Details
(Keywords: dev-doc-needed)
Attachments
(1 file)
4.65 KB,
text/x-log
|
Details |
When trying to install unsigned addons from a localhost, it fails and we don't see any information signifying failure.
STR:
- Build an addon locally (e.g. https://github.com/leibovic/instagram-panel/ or https://github.com/mfinkle/clicktoviewimages)
- Install it using the bootstrap install script.
- Observe on the device that a new tab opens pointing to the xpi file.
- Observe there is no doorhanger that shows up asking to verify the install.
Notes:
- The current workaround is to install the addon via a webserver (people.mozilla.org works file) that serves the addon and only then do you see the security doorhanger asking you if you want to install this addon.
- See attached logs.
- This seems to work from builds before 21/08
Updated•9 years ago
|
Summary: Installing unsigned addons fails when xpinstall.signatures.required is false → Installing via direct links to unsigned addons XPI fails when xpinstall.signatures.required is false
Comment 1•9 years ago
|
||
This is an expected result of bug 1042699 and is unrelated to signing.
Summary: Installing via direct links to unsigned addons XPI fails when xpinstall.signatures.required is false → Installing via direct links to addons XPI fails
(In reply to Dave Townsend [:mossop] from comment #1)
> This is an expected result of bug 1042699 and is unrelated to signing.
So, if it is the expected result to block the XPI addons, then "The current workaround is to install the addon via a webserver (people.mozilla.org works file)" is a bug? You shouldn't be able to install via webserver?
As for the doorhanger issue, I've logged bug 1201547
Comment 3•9 years ago
|
||
(In reply to Mihai Pop from comment #2)
> (In reply to Dave Townsend [:mossop] from comment #1)
> > This is an expected result of bug 1042699 and is unrelated to signing.
>
> So, if it is the expected result to block the XPI addons, then "The current
> workaround is to install the addon via a webserver (people.mozilla.org works
> file)" is a bug? You shouldn't be able to install via webserver?
No, installing from a webpage should continue to work. Installing by directly opening an XPI in a tab is what has stopped working.
Comment 5•9 years ago
|
||
It's a "apparently there isn't a safe way to do this" bug.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(dtownsend)
Resolution: --- → WONTFIX
Comment 6•9 years ago
|
||
We should update our boilerplate add-on build script then, since that depends on this now obsolete functionality.
Any ideas for a good developer flow for mobile add-on developers to test their add-ons? Are there any plans for some sort of remote devtools integration to test add-ons?
Flags: needinfo?(dtownsend)
Comment 7•9 years ago
|
||
(In reply to :Margaret Leibovic from comment #6)
> We should update our boilerplate add-on build script then, since that
> depends on this now obsolete functionality.
>
> Any ideas for a good developer flow for mobile add-on developers to test
> their add-ons? Are there any plans for some sort of remote devtools
> integration to test add-ons?
No I wasn't aware you were using this approach. There are tools like the extension auto installer that might help (https://github.com/palant/autoinstaller). But yes ideally using a remote devtool or something would be nice.
Flags: needinfo?(dtownsend)
Updated•9 years ago
|
Flags: qe-verify+
QA Contact: vasilica.mihasca
Comment 8•9 years ago
|
||
(In reply to Dave Townsend [:mossop] from comment #7)
> (In reply to :Margaret Leibovic from comment #6)
> > We should update our boilerplate add-on build script then, since that
> > depends on this now obsolete functionality.
> >
> > Any ideas for a good developer flow for mobile add-on developers to test
> > their add-ons? Are there any plans for some sort of remote devtools
> > integration to test add-ons?
>
> No I wasn't aware you were using this approach. There are tools like the
> extension auto installer that might help
> (https://github.com/palant/autoinstaller). But yes ideally using a remote
> devtool or something would be nice.
Yeah, the approach we've been using is to push the file to the sdcard, then load Fennec with a file URI:
https://github.com/mozilla/firefox-for-android-addons/blob/master/boilerplate/native-ui-boilerplate/build#L24
We should brainstorm ways to improve this flow, especially since it won't work anymore!
Comment 9•9 years ago
|
||
This affects all platforms.
Component: Add-on Manager → Add-ons Manager
Product: Firefox for Android → Toolkit
Version: Firefox 43 → Trunk
Updated•9 years ago
|
Blocks: CVE-2015-4498
Comment 11•9 years ago
|
||
Jonathan: To install one or more add-ons found as *.xpi files in one directory on your hard disk, click "Install add-on from file…" in the rolldown widget near top right of the add-ons manager. This way you can install any number of them in one operation by using shift-click or ctrl-click in the file picker.
Reporter | ||
Comment 12•9 years ago
|
||
(In reply to Tony Mechelynck [:tonymec] from comment #11)
> Jonathan: To install one or more add-ons found as *.xpi files in one
> directory on your hard disk, click "Install add-on from file…" in the
> rolldown widget near top right of the add-ons manager. This way you can
> install any number of them in one operation by using shift-click or
> ctrl-click in the file picker.
The original issue was posted as an Android issue. The default behaviour of clicking a link to an addon is to open it in a new tab which currently doesn't do anything. (There isn't a Ctrl button either :)
See Also: → 1211931
Comment 14•9 years ago
|
||
https://developer.mozilla.org/en-US/Add-ons/Firefox_for_Android/Walkthrough#Installing_the_add-on needs to be updated with current instructions on how to install an add-on in Firefox for Android.
Comment 15•9 years ago
|
||
(In reply to Alex Vallat from comment #14)
> https://developer.mozilla.org/en-US/Add-ons/Firefox_for_Android/
> Walkthrough#Installing_the_add-on needs to be updated with current
> instructions on how to install an add-on in Firefox for Android.
It would be wonderful if we could fix bug 1211931 and update the docs to use that... but in the meantime, we should probably tell people to push an HTML page to the device. I have an example of that here:
https://github.com/leibovic/fennec-fxos-tv/blob/master/build
I'll aim to update the docs this week. NI so I don't forget.
Flags: needinfo?(margaret.leibovic)
Keywords: dev-doc-needed
Comment 16•9 years ago
|
||
(In reply to :Margaret Leibovic from comment #15)
[...]
> I'll aim to update the docs this week. NI so I don't forget.
Apparently you did, but forgot to clear the NEEDINFO?
Blocks: 1230292
Comment 18•9 years ago
|
||
(In reply to Tony Mechelynck [:tonymec] from comment #16)
> (In reply to :Margaret Leibovic from comment #15)
> [...]
> > I'll aim to update the docs this week. NI so I don't forget.
>
> Apparently you did, but forgot to clear the NEEDINFO?
I didn't update the docs, but I did update the boilerplate code just now:
https://github.com/mozilla/firefox-for-android-addons/commit/bc2ff3c8f93cf7922957d089541500efb556418d
Flags: needinfo?(margaret.leibovic)
You need to log in
before you can comment on or make changes to this bug.
Description
•