1592269 - Failed to acquire a new OAuth token for @gmail.com

Status: RESOLVED DUPLICATE of bug 1592407

(Thunderbird :: Add-Ons: Extensions API, defect)

Description

[r4czek]

Attachment: request.png

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0

Steps to reproduce:

Attempted to add a new, network, Google Calendar.

In calendar tab:

1. Right click in Calendars section > New Calendar...
2. On the Network
3. Google Calendar
4. Defined my Google e-mail (let's say it was "[e-mail]")

At this point Google's authentication window popped up
5. I've entered my Google e-mail again
6. I've entered my Google password

At this point I was presented with request from "Provider for Google Calendar" to access my Google calendar & tasks (see: "request.png").
7. I clicked "Allow"

Versions:
Thunderbird: 68.2.0 (32-bit)
Lightning: 68.2.0
Provider for Google Calendar: 68.0

Logs for the whole process:
Handler function DebuggerProgressListener.prototype.onWindowCreated threw an exception: TypeError: window is undefined
Stack: getWindowID@resource://devtools/server/actors/targets/browsing-context.js:83:3
DebuggerProgressListener.prototype.onWindowCreated<@resource://devtools/server/actors/targets/browsing-context.js:1661:21
exports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:111:22
_fireEvent@chrome://global/content/bindings/wizard.xml:413:26
set_currentPage@chrome://global/content/bindings/wizard.xml:89:16
advance@chrome://global/content/bindings/wizard.xml:282:15
wizard_XBL_Constructor@chrome://global/content/bindings/wizard.xml:197:14
openCalendarWizard@resource://calendar/modules/utils/calWindowUtils.jsm:26:12
doCommand@chrome://calendar/content/calendar-common-sets.js:375:20
goDoCommand@chrome://global/content/globalOverlay.js:101:18
oncommand@chrome://messenger/content/messenger.xul:1:1
Line: 83, column: 3 ThreadSafeDevToolsUtils.js:90:13
reportException resource://devtools/shared/ThreadSafeDevToolsUtils.js:90
makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:117
_fireEvent chrome://global/content/bindings/wizard.xml:413
set_currentPage chrome://global/content/bindings/wizard.xml:89
advance chrome://global/content/bindings/wizard.xml:282
wizard_XBL_Constructor chrome://global/content/bindings/wizard.xml:197
openCalendarWizard resource://calendar/modules/utils/calWindowUtils.jsm:26
doCommand chrome://calendar/content/calendar-common-sets.js:375
goDoCommand chrome://global/content/globalOverlay.js:101
oncommand chrome://messenger/content/messenger.xul:1
Handler function DebuggerProgressListener.prototype.onWindowCreated threw an exception: TypeError: window is undefined
Stack: getWindowID@resource://devtools/server/actors/targets/browsing-context.js:83:3
DebuggerProgressListener.prototype.onWindowCreated<@resource://devtools/server/actors/targets/browsing-context.js:1661:21
exports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:111:22
_fireEvent@chrome://global/content/bindings/wizard.xml:413:26
set_currentPage@chrome://global/content/bindings/wizard.xml:89:16
advance@chrome://global/content/bindings/wizard.xml:282:15
connectedCallback/listeners<@chrome://global/content/elements/wizard.js:50:49
openCalendarWizard@resource://calendar/modules/utils/calWindowUtils.jsm:26:12
doCommand@chrome://calendar/content/calendar-common-sets.js:375:20
goDoCommand@chrome://global/content/globalOverlay.js:101:18
oncommand@chrome://messenger/content/messenger.xul:1:1
Line: 83, column: 3 3 ThreadSafeDevToolsUtils.js:90:13
reportException resource://devtools/shared/ThreadSafeDevToolsUtils.js:90
makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:117
_fireEvent chrome://global/content/bindings/wizard.xml:413
set_currentPage chrome://global/content/bindings/wizard.xml:89
advance chrome://global/content/bindings/wizard.xml:282
listeners chrome://global/content/elements/wizard.js:50
openCalendarWizard resource://calendar/modules/utils/calWindowUtils.jsm:26
doCommand chrome://calendar/content/calendar-common-sets.js:375
goDoCommand chrome://global/content/globalOverlay.js:101
oncommand chrome://messenger/content/messenger.xul:1
Lightning: [calGoogleSessionManager] Reusing session [e-mail] gdataSession.jsm:78
Lightning: [calGoogleSession] Token expired 1572357588 seconds ago, resetting gdataSession.jsm:357
Lightning: [calGoogleCalendar] Logging in session [e-mail] gdataSession.jsm:247
Lightning: [calGoogleCalendar] No access token for [e-mail], refreshing token gdataSession.jsm:318
Lightning: [calGoogleSession] Adding item https://www.googleapis.com/tasks/v1/users/@me/lists to queue gdataSession.jsm:374
Lightning: [calGoogleSession] Adding item https://www.googleapis.com/calendar/v3/users/me/calendarList to queue gdataSession.jsm:374
Lightning: [calGoogleCalendar] Failed to acquire a new OAuth token for [e-mail] data: undefined gdataSession.jsm:257
Lightning: [calGoogleSession] Authentication failure: undefined gdataSession.jsm:282
[Exception... "null" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://gdata-provider/modules/gdataSession.jsm :: login/authFailed< :: line 284" data: no] gdataSession.jsm:284:33
authFailed resource://gdata-provider/modules/gdataSession.jsm:284
<anonymous> self-hosted:1001
onPromptAuthAvailable resource://gdata-provider/modules/gdataSession.jsm:301
onAccessTokenFailed resource://gdata-provider/modules/OAuth2.jsm:240
onAccessTokenFailed self-hosted:1007
onload resource://gre/modules/Http.jsm:77
openCalendarWizard resource://calendar/modules/utils/calWindowUtils.jsm:26
doCommand chrome://calendar/content/calendar-common-sets.js:375
goDoCommand chrome://global/content/globalOverlay.js:101
oncommand chrome://messenger/content/messenger.xul:1

Actual results:

I was presented with empty "locate your calendar" window.

Expected results:

I was expecting to see a list of calendars defined on my Google e-mail account.

Comment 1

[Dan Harkless]

Yeah, this bug appears to be quite serious, and is not limited to the calendar functionality (also the component shouldn't be Add-Ons: Extensions API).

Some months back, automatic mail-checking ceased working for me on my Thunderbird 60.x Gmail + Yahoo! dual-account profile (manually pressing Get Messages continued to work fine). Therefore, when I saw in the update notification that 60.9.0 was the last 60.x version, I decided to install 68.2.0 from scratch, as the 64-bit version, manually changing the install directory to be under Program Files so I could leave the old 32-bit 60.x version in Program Files (x86) in case I needed to revert to it. And finally, I created a fresh profile for use with the 68+ versions.

Upon starting up 68.2.0 for the first time, it prompted me for email account credentials, and I entered my login info for Gmail. It popped up the web browser mini-window for me to log in to obtain an OAuth token. After entering username, password, and hitting the button to allow Gmail to access my Gmail data, I got a popup window saying "Authentication failure while connecting to server imap.gmail.com". I tried several more times, including quitting and restarting Thunderbird multiple times (in the past I've sometimes observed that when my Internet connection is slow, Thunderbird falsely claims I have an authentication failure, when in fact, it apparently just hit a timeout, yet it almost always works after quitting and restarting — different timeout value used there...?), but same result every time. I have not yet attempted to set up my Yahoo! Mail account under Thunderbird 68.2.0.

My Thunderbird 60.9.0 32-bit install continues to work fine (though it's possible that if I created a fresh profile there, I'd hit the same problem — let me know if you need me to test that).

Comment 2

[Dan Harkless]

Oh, and I did not do this with the 32-bit and 64-bit versions running simultaneously; I've always quit one and made sure its process was gone from the Task Manager before running the other. I am on Windows 7 64-bit, BTW.

Comment 3

[Dan Harkless]

And sorry, in my first comment, "allow Gmail to access my Gmail data" should've read "allow Thunderbird to access my Gmail data". One last note is that I did not install the automatic update service with either the 32-bit or 64-bit versions, so any interference from that can be ruled out.

Comment 4

[Jorg K (CEST = GMT+2)]

Please note that "Provider for Google Calendar" is an add-on and that issues should be reported at https://github.com/kewisch/gdata-provider. However, the IMAP failure is more severe. I guess that was just reported in bug 1592407.