Closed Bug 1469743 Opened 6 years ago Closed 6 years ago

Updating browser apparently causes add-ons to lose their "link" to AMO

Categories

(Toolkit :: Add-ons Manager, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: bruce.bugz, Unassigned)

Details

Attachments

(4 files)

It appears that my add-ons are losing their "link" to AMO. So what happens is that the add-ons continue working perfectly fine, but at about:addons, they are all missing their AMO ratings, and some of them are missing their author names, icons etc., supposedly because they weren't included in the add-on manifest but were being fetched remotely. I would assume this also breaks their updating.

I noticed this a couple of days back for the first time. Manual (re)installation of the add-ons from AMO on top of the existing 'orphaned' add-ons had seemed to make things work (even across restarts) but now the issue is back again. I'm not 100% sure but updating the browser is probably what triggers the issue. I will try and test some more.

I don't have CCleaner or any 'clean-up' programs interfering. I have Windows Defender and Comodo Firewall. Doesn't look like either of them is responsible. I'm using a small CSS snippet through userContent.css but I have verified that it is not responsible:

    @-moz-document url("about:addons") {
        /* move description below settings */
        scrollbox[type="extension"] #detail-grid {
            -moz-box-ordinal-group: 1 !important;
        }
        scrollbox[type="extension"] #detail-contributions {
            -moz-box-ordinal-group: 2 !important;
        } 
        scrollbox[type="extension"] #detail-desc-container {
            -moz-box-ordinal-group: 3 !important;
        }	
    }
Attached file about-support.txt
Component: General → Add-ons Manager
Product: Firefox → Toolkit
Flags: needinfo?(aswan)
I can't reproduce this locally, but if you're willing, the following would be helpful:
1. Go to about:config and set two preferences:
  a. set devtools.chrome.enabled to true
  b. set extensions.logging.enabled to true
2. Open the browser console (https://developer.mozilla.org/en-US/docs/Tools/Browser_Console)
3. Enter the following two lines in the browser console:

ChromeUtils.import("resource://gre/modules/addons/AddonRepository.jsm")
AddonRepository.backgroundUpdateCheck()

You should see a bunch of logging in the browser console at this point, if you can copy and paste that into a comment or attachment on this bug, that should point to what's going wrong.
Flags: needinfo?(aswan) → needinfo?(ampersand100000)
I had created a new profile after filing the issue and I am unable to reproduce the issue now.

If I run into it again, I will post the log here.
Flags: needinfo?(ampersand100000)
Please re-open if you can reproduce and gather the requested information.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: