When the extension could be updated by Firefox?

In Firefox 40.0.3, when update old unsigned Firefox Add-on to newer signed version application, the version information in Firefox Extension page still old and the extention would be disabled since it could not be verified. Firefox 40.0.3 still load the old unsigned version.
It looks the profile file wasn’t updated immediately.
C:\Users\amspqa\AppData\Roaming\Mozilla\Firefox\Profiles[default profile]\extensions.json
But after waiting for about 20 mins, the newer signed version would be loaded.

I would like to know

  1. When the extension could be updated by Firefox?
  2. Is there any way we could make Firefox update immediately?

Firefox checks for updates once a day, which should be enough for the majority of users to update to the signed version fairly quickly. We generally don’t allow tampering with the update process, particularly if your add-on is listed on AMO.

Users can go to the extension tab in about:addons and choose to check for updates manually if they’re concerned.

Thank you. But my add on is unlisted, it would not work by checking for update manually

For unlisted Add-on (install by application), we uninstall old unsigned Add-on and install newer signed version, but the new signed version can’t be verified immediately. In this case. Is there any way we could make Firefox verify new Add-on immediately?
In some environment it could be verified immediately, but others are not be verified immediately. Is there any thing to trigger the verification?

The signing certificate is checked by Firefox when an add-on is about to be installed.
So it either gets verified and the add-on gets installed or if the signature verification fails, the add-on will not get installed (or maybe installed and immediately disabled, not sure).

Update Firefox to 40.0.3 and the Add-on become not be verified since it’s unsigned.(Ref. P1.png)
We uninstall the unsigned Add-on and install signed Add-on to Firefox. But the Add-on still show not be verified. (the same as P1.png)
We fould the profile isn’t updated immediately
C:\Users\amspqa\AppData\Roaming\Mozilla\Firefox\Profiles[default profile]\extensions.json (Ref. P3.png)
But after waiting for about 20 mins, the newer signed version would be verified and loaded.

I would like to know is there any way we could make Firefox update and load the signed Add-on immediately?
P1.png


P3.png

No double posting please, merging with existing thread.

Is the addon signed? Is the xpi you’re using to install the signed copy?

Yes, the xpi is trend_micro_osprey_firefox_extension-2.0.0.1083-fx-windows.xpi
The binary files in the folder already update to 2.0.1083. But Firefox Extention Page still show 2.0.1082.

I’m going to poke @TheOne on this as admins are the ones that review binary addons, and TheOne has reviewed the majority of unlisted addons.

I don’t really know what the issue is. It’s best to file a bug at https://bugzilla.mozilla.org/ and sort it out with Firefox developers.