Closed Bug 813990 Opened 12 years ago Closed 7 years ago

Updater never checks for updates to Provider for Google Calendar

Categories

(Toolkit :: Add-ons Manager, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jamesrome, Unassigned)

References

Details

The update from 16.02 to 17.0 is the most traumatic I have ever experienced from Mozilla. The updater supposedly checks for extension update. It finds enigmail and lightning. But then when you start Thunderbird, your Google Calendar is blank until you check again for updates and update the Provider for Google Calendar.

Most users would assume that everything is up to date after the install process!
Component: Installer → Add-ons Manager
Product: Thunderbird → Toolkit
Version: 17 → Trunk
I've had this reported from quite a few users. The new version was public even before the Lightning release. I'd really like to ease the pain for users here, why is the update checker not finding the update?
Hmm, I can't reproduce this with the following steps:
* Install Thunderbird 16.0.2
* Install Lightning 1.8
* Provider for Google Calendar 0.17
* Update Thunderbird to 17.0

For me, everything automatically updated correctly (on Windows 7).


To confirm: After updating, opening the Add-ons Manager and manually checking for updates correctly found the update?


If this is still reproducible for anyone else, I'll need some additional info:
* Running Thunderbird 16.0.2, with Lightning 1.8 and Google Calendar 0.17 installed
* Open about:config via Preferences -> Advanced -> Config Editor, set extensions.logging.enabled to true
* Update Thunderbird to 17.0
* Open the Error Console (Tools -> Error Console), and copy everything and paste it into a txt file and attach it here
* Clear the Error console
* Open Add-ons Manager (Tools -> Add-ons)
* Check for updates
* Once that's completed, use the above step to again copy everything from the Error Console, and attach it here
Possibly this is due to the mitigation jorgev put in place for me, that blocks version 0.17 with Thunderbird 17. This is not something we can do every version though, so I'd still be interested in a solution.

Do you think it makes sense to temporarily remove this blocklisting to reproduce the issue?
Blair: That is not the scenario. The install process itself checks for updates and updates enigmail and lightning, but not provider. So the user thinks all is up to date. But if you then check updates, it indeed finds the Provider update.
Maybe problem is that both version are (were) marked as compatible with Thunderbird 17?
... Version 0.17 ... Works with SeaMonkey 2.12 and later, Thunderbird 15.0 and later
... Version 0.18 ... Works with SeaMonkey 2.14 and later, Thunderbird 17.0 and later

If I remember correctly during update Thunderbird checks for incompatible extensions. Maybe the search for updates is done only for the few incompatible extensions and not for all extensions?
James, 
Does this still happen for you with current versions?
Flags: needinfo?(jamesrome)
No, since calendar keeps working. But not looked explicitly
Flags: needinfo?(jamesrome)
Thanks for commenting. Whatever it was then, apparently no longer an issue
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.