-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebExtension can't installed in Firefox 62.0 by not correctly signed problem #1367
Comments
It was my understanding that you cannot install unsigned addons following Firefox 57, except in Developer Edition. Regardless, you don’t say how you install your addons. Installing any addon with Marionette should work, since it bypasses this security constraint, but they need to be passed to the
|
@andreastt The extension was already signed by "upload add-on through the Developer Hub on AMO" following https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Distribution. I installed it with following code, it can be installed success in Firefox 61 but can't installed in Firefox 62.
|
As when I get SeleniumHQ/selenium#5069 right, there is no support yet in the Selenium Python client to install an addon which is based on the WebExtension API. So I don't see how this should have worked at all in Firefox 61. |
@whimboo This is java but not python. it's not the same problem with SeleniumHQ/selenium#5069 |
I download a XPI file from https://addons.mozilla.org/en-US/firefox/addon/search-encrypt/?src=hp-dl-promo. And try to install it with the same Java code, the same error happened. Java code
Error log
|
The error message is still the same:
I don’t know if it’s supposed to be possible to install signed-addons by putting it manually in the profile. If the addon is indeed signed correctly, Firefox appears to disagree about that fact. In any case this is not a geckodriver problem. Filing a bug against the Web Extensions component in Bugzilla would be the next step if you believe this is a bug. |
Seems it's problem of selenium Java . The same environment and same test case, I replace java code with nodejs code, it works fines. |
OK, then it sounds like the Selenium Java client is putting the extension in the wrong place. I would file a bug. |
I open a issue in selenium. SeleniumHQ/selenium#6403 . It's reproduced, but they said it's not problem of selenium. |
I can reproduce the issue, this sample works well in 60 (ESR), 63 (Dev) and 64 (Nightly), but it fails in 63 (Release). Here are the trace logs for all these versions: P.S. Note an extension shutdown issue in Nightly that does not exist in other versions |
@andreastt What's the correct place for extensions? We did not change profile serialization code for years, why did it stop working now? |
I don’t know the right location. |
@barancev were you using geckodriver 0.22.0 for those tests? If yes, can you also please test with the 0.21.0 release? |
@whimboo I created this issue with geckodriver 0.21.0. |
@whimboo Yes, it's reproducible with geckodriver 0.21 |
Open a issue in Firefox Bugzilla https://bugzilla.mozilla.org/show_bug.cgi?id=1493069 |
Thanks. Lets follow-up there. |
@whimboo Andrew Swan as following question in mozilla bugzilla, can you help to answer ?
|
It has been all discussed on the bug. So this issue is indeed invalid. |
This issue has been automatically locked since there has not been any recent activity after it was closed. If you have run into an issue you think is related, please open a new issue. |
System
Testcase
I have several web-extensions , those works fine in Firefox 61, but after upgrade to Firefox 62 , those can't not be installed by "not correctly signed" problem. I also can install the extension manually in firefox 62 without selenium and geckodriver .
This is manifest of one extension.
Trace-level log
The text was updated successfully, but these errors were encountered: