Open SergeLalonde opened 1 year ago
Hi There,
Got the same issue, owl for exchange unable to login. To solve it for me, i've juste have to disable expression search and restart.
To me, it's because owl open new tab at the start to login in to the exchange server. And for me this new tab is desperately empty.
It's hard to get log content has it's happen at TB start.
When i'm disabling owl, start console and re-enabling it, i've got -apparently- the same issue and the error in console :
getTabWindow(...).document is undefined 2 [ext-mail.js:216](chrome://messenger/content/parent/ext-mail.js)
getTabTabmail chrome://messenger/content/parent/ext-mail.js:216
get tabmail chrome://messenger/content/parent/ext-mail.js:1465
get index chrome://messenger/content/parent/ext-mail.js:1470
convert chrome://extensions/content/parent/ext-tabs-base.js:626
convert chrome://messenger/content/parent/ext-mail.js:1177
convert chrome://extensions/content/parent/ext-tabs-base.js:2044
create chrome://messenger/content/parent/ext-tabs.js:539
InterpretGeneratorResume self-hosted:1455
AsyncFunctionNext self-hosted:852
(Asynchrone : async)
createTabWithCookieStoreId jar:file:///C:/Users/meUser/AppData/Roaming/Thunderbird/Profiles/me.profile/extensions/owl@beonex.com.xpi!/webapi/uitweaks/uitweaks.js:133
AsyncFunctionNext self-hosted:852
(Asynchrone : async)
result resource://gre/modules/ExtensionParent.sys.mjs:1144
withCallContextData resource://gre/modules/ExtensionParent.sys.mjs:627
result resource://gre/modules/ExtensionParent.sys.mjs:1143
withPendingBrowser resource://gre/modules/ExtensionParent.sys.mjs:637
result resource://gre/modules/ExtensionParent.sys.mjs:1142
callAndLog resource://gre/modules/ExtensionParent.sys.mjs:1095
recvAPICall resource://gre/modules/ExtensionParent.sys.mjs:1141
AsyncFunctionNext self-hosted:852
(Asynchrone : async)
_recv resource://gre/modules/ConduitsChild.sys.mjs:77
receiveMessage resource://gre/modules/ConduitsParent.sys.mjs:453
To me it's close to https://github.com/opto/Expression-Search-NG/issues/86#issuecomment-1803457905 (same symptom)
Expression Search v4.0.13 TB 115.4.3/64 Owl 1.2.3
Thanks for the confirmation @Bbillyben! At least I'm not alone. For some of opto's plugins, I immediately get an empty tab. For others, it asks for the Exchange login information and then gets the empty tab and never completed the authentification. My workaround is to disable Expression Search, XNote++, Nostalgy++, and ImportExport Tools. Then disable OWL and reenable it to force it to log in. Once the login is complete, I reenable the opto plugins. Annoying, but workable for now.
I can confirm the same issue (Expression Search v4.0.15, TB 115.5.1, Owl 1.2.3 on Ubuntu 23.10). Having Expression Search enabled breaks the Owl MFA login procedure. Disabling Expression Search fixes the problem with Owl.
Same issue for me. Owl 1.2.3, Expression search 4.0.18, TB 115.5.1 (64-bit) on Windows 10.
@opto Any updates on this issue? Thanks.
Exactly the same issue here. OWL 1.2.4, Expression search NG 4.0.34, TB 115.10.1 (64-bit) This issue is critical for me. If I cannot use OWL with Expression search I will be obliged to change to Outlook.
@opto Any updates on this issue? Thanks.
I've discovered why I'm suddenly unable to log into my company's Exchange email server with the 2-factor authentication using the OWL plugin. It seems that Nostalgy++ 4.1.2 is somehow blocking the 2-factor authentication from completing. Maybe there's a timeout in Nostalgy++ that is interfering with OWL or authentification? When I start TB, I get the Outlook login window, and when I do the 2-factor, it then stays stuck and never completes. If I disable Nostalgy++, there's no problem. I noticed that XNote++ 4.1.8 and Expression Search - NG 4.0.15 also cause the same issue. In fact, Expression Search - NG is even worse because it somehow completely blocks the Outlook login window from ever loading. Since all three of these addons are opto's, perhaps there's some common code in them that is causing this? This is a recent development and it was working just a few days ago. My workaround is to disable all 3 of these addons, restart TB, login to Exchange, then re-enable the addons. I'm using TB 115.4.3 (64-bit) on Windows 11. Thanks.