Archive for March, 2015
I uploaded version 2.0.1 for review today. It should fix the most common issues with version 2.0, mainly it switches over to using a special URI that instructs Google to change the document title instead of redirecting to localhost.
- Added validation to prevent duplicate login errors
- Updated authentication to no longer require a redirect to localhost. That method didn’t work in a web server or other application was listening on port 80.
- Fix: Next button in new account wizard with new account not always disabled
- Fix: AB not displayed in new account dialog after having its synced username cleared
- Added the cs locale courtesy of Michal Stanke
- Added the es-ES locale courtesy of Scooter
- Added the it locale courtesy of Leopoldo Saggin
A few people have had trouble authenticating with version 2.0. Google deprecated the old method called ClientLogin, so version 2 switched over to OAuth2, which is more secure since you don’t have to provide the application with your password.
The most common causes are an application listening on port 80 (a web server, skype, etc.), not allowing cookies and using a proxy.
Please follow these steps if you are having trouble authenticating:
- Update to version 2.0.3 – this version has a fix for the expired token dialog. 2.0.1 change the authentication method so it would work even when an application was listening on port 80 (such as a web server or skype)
- Go to the Menu -> File -> Offline and verify Work Offline is not checked
- Go to Menu -> Options -> Privacy. Either check Accept cookies from sites (Accept third-party cookies can be set to Never) or click Exceptions… and add google.com and click Allow. You may need to clear cookies and clear all exceptions first.
- Disable all other add-ons and restart Thunderbird. Lightning + the Google Calendar Provider add-on have caused this issue in the past.
- Go to Menu -> Options -> Advanced -> Network & Disk Space -> Click on Settings -> choose No Proxy. Restart Thunderbird and try again.
If none of the above works, please enable verbose logging in the gContactSync Preferences, try to authenticate again, then send me the log. Also try clicking on this link in a web browser and see if it eventually redirects you to a blank page with an address localhost/?code=…. That link is what gContactSync uses to authenticate.
I recently released version 2.0.0 of gContactSync. This is a mandatory upgrade for all users since Google is discontinuing the authentication method that previous versions used.
The first time you use version 2.0.0 or later you will have to reauthenticate each unique account you synchronize (once per e-mail address, not synchronized address book). Unfortunately gContactSync cannot use your saved e-mail password from Thunderbird any more with OAuth2.
- Switches to OAuth2. This is a more secure method of authentication and won’t require application-specific passwords for accounts using 2-step authentication.
- Throttles requests that upload photos to Google. This will prevent 503 errors when uploading several new photos in a short period of time, or photos appearing to not be synchronized.
- Synchronization is now done in a worker thread to improve responsiveness while synchronizing.