1304286 - Chrome not defined after installing signed plugin

Status: RESOLVED WORKSFORME

(Toolkit :: Add-ons Manager, defect)

Description

[jeroen.delau]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:48.0) Gecko/20100101 Firefox/48.0
Build ID: 20160823121617

Steps to reproduce:

- Installed the plugin as temporary add-on for debugging
- Once working, removed that plugin
- Uploaded zipped plugin to AMO
- Downloaded it using link in AMO dashboard


Actual results:

- Plugin options page didn't run said "chrome is not defined"

- After restarting Firefox, plugin worked.

I actually had this before and I was banging my head against the wall trying to figure out what went wrong. I spent much time checking if Firefox got updated, if I made an error in packaging. It just appeared so random.


Expected results:

- Singed plugin should run without interruption
- Some sort of warning that helps other users know that they should restart the browser

Comment 1

[Andrew Swan [:aswan]]

Can you please attach or include a link to your extension?  (I'm assuming that where you wrote "plugin" above you meant extension?)

Comment 2

[jeroen.delau]

Aaah yes, I meant extension.

The original extension can't be used. But I create a small test plugin that should demonstrate the issue:
https://dl.dropboxusercontent.com/u/18297766/fftest.zip

Comment 3

[jeroen.delau]

Extension, text extension is what I meant to write...

(In reply to jeroen.delau from comment #2)
> Aaah yes, I meant extension.
> 
> The original extension can't be used. But I create a small test plugin that
> should demonstrate the issue:
> https://dl.dropboxusercontent.com/u/18297766/fftest.zip

Comment 4

[Andrew Swan [:aswan]]

(In reply to jeroen.delau from comment #0)
> Steps to reproduce:
> 
> - Installed the plugin as temporary add-on for debugging
> - Once working, removed that plugin
> - Uploaded zipped plugin to AMO
> - Downloaded it using link in AMO dashboard

I can't reproduce this with Nightly but I do have a question.  At the second step (removed that plugin), did you uninstall the extension from about:addons?  Or just remove it from the filesystem?
If you didn't actually uninstall it in the running browser, then you have the extension installed temporarily at the same time you're trying to install it permanently.  Its possible that we're doing something wrong in that situation, but like I said, using Nightly I am unable to reproduce the error you reported.

Comment 5

[Robert Helmer [:rhelmer]]

I think this might be a dupe of a bug I found recently, going to take this one and investigate and will dupe if so.

Comment 6

[jeroen.delau]

All installing and uninstalling was done through:
about:debugging#addons
about:addons

But, indeed, now that I look again I can't reproduce it with the above steps. It still happens though, I'm looking at it right now, but it is indeed hard to find the exact steps that cause it.

It is related to installing/removing multiple versions of the same plugin though.

Comment 7

[CosminB]

:rhelmer do you have have any news about the investigation?

I was unable to reproduce this issue on:
User agent:Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0 
Build id: 20161214030231  

User agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:53.0) Gecko/20100101 Firefox/53.0
Build id: 20161215030215

Comment 8

[Andrew Swan [:aswan]]

The STR sound very similar to bug 1316441

Comment 9

[Robert Helmer [:rhelmer]]

I can't reproduce either (and it's not the bug I was trying to track down that I alluded to in comment 5)

Comment 10

[CosminB]

Using the steps from the description of this bug and the steps from bug 1316441 still can’t reproduce this issue. I can only see this http://screencast.com/t/a7VRvQbWkOq 

Considering the fact that none of us reproduces this bug I will mark it as WFM.
If anyone can reproduce it, feel free to reopen the issue and provide more information.