I'm trying to debug Outlook addin in the desktop mode.
node v14.18.3 32-bit
Microsoft® Outlook® 2019 MSO (Version 2110 Build 16.0.14527.20234) 32-bit
Windows 10
launch.json:
{
"name": "Outlook Desktop (Edge Legacy)",
"type": "office-addin",
"request": "attach",
"url": "https://localhost:3000/taskpane.html?_host_Info=Outlook$Win32$16.01$en-US$$$$0",
"port": 9222,
"timeout": 600000,
"webRoot": "${workspaceRoot}",
"preLaunchTask": "Debug: Outlook Desktop",
"postDebugTask": "Stop Debug",
}
I'm getting the following error:
[vscode-debugger-extention-for-office-addins] Error processing "attach": connect ECONNREFUSED 127.0.0.1:9222
In my addin I got the info about a webview user agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64; WebView/3.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Edge/18.19044
So I used npx office-addin-dev-settings webview .\manifest.xml edge-legacy to set up the correct webview. The error is still there. I would appreciate any suggestions on how to solve this problem.
The browser used by Office Add-ins depends on both your computer's OS and the version of Office you are using, as documented here. You are using Windows 10 and Outlook 2019, so you should be using IE as your browser. The Microsoft Office Add-in Debugger Extension for Visual Studio Code allows you to debug your Office Add-in against the Microsoft Edge with the original webView (EdgeHTML) runtime. For instructions about debugging against Internet Explorer, see this article.
Most probably you still got Internet Explorer used by Outlook for running web add-ins. There are several factors that could cause this on your side. You could have:
Non-subscription versions of Office for Windows. These will continue to use Internet Explorer 11 as the web viewer.
Office running on versions of Windows 10 lower than 1903. These will also continue to use Internet Explorer 11.
Versions of Office lower than 16.0.11629. These will also continue to use Internet Explorer 11.
It is also not clear what Windows build number you have got installed on the system. So, I'd recommend installing the latest updates for the OS and Outlook. Also you need to make sure you are using Office 365 version of Outlook.
Beginning with Office 365 version 16.0.11629 and Windows 10 version 1903, Office Add-ins running on Office 365 for Windows will use a Microsoft Edge WebView as the runtime.
As soon as you can install the required software you will be eligible to use the Microsoft Edge DevTools extension in VSCode.
Related
I have an Add-in I have written for Microsoft Outlook. The Add-in runs in a task pane. I have a button on the html in the page that opens a new window using Office.context.ui.displayDialogAsync. This button works fine in the web client, but when clicked in the full Outlook client, a window appears and disappears in a split second. This Add-in was developed outside VS so not sure how I can debug apart from in web client, which not does have the issue.
The domain is the same, and the domain is in the appDomain of the XML manifest. The URL is also https.
Does anyone have any ideas, have I missed something that says this isn't available in full client and only available in web client?
About Outlook version:
Version 2102 (Build 13801.21004 Click-to-Run)
Microsoft Office for Outlook 365 MSO (16.0.13801.21002) 64-bit
If I clock Office Updates, it tells me Office is up to date.
Update
I have another machine with Outlook installed, and I have discovered the dialog opens fine on the full outlook client. Looking at the version for that version of outlook (logged in to the same Office 365 account), the version shows as:
Version 2110 (Build 14527.20226 Click-to Run)
Microsoft Office for Outlook 365 MSO (Version 2110 Build 16.0.14527.20168) 64-bit
So it looks like maybe the earlier build had an issue in Outlook?
Would you like to share a screen recording in the machine where the API is not working?
Besides, you could also try a test add-in with this: Manifest.
It's an app command so you can click "Show Taskpane" first, and then click "launchDialogSameOrigin" button in the taskpane. You can observe whether the dialog is working correctly in this add-in.
Thanks.
Please help me with the following issue.
I developed an Outlook add-in that works great on the following platforms:
Mac os
Windows 10
Windows 8.1
However, a client of mine installed it on Windows Server 2016 with Office 2019 and it doesn't seem to work. It stops at the loading screen. I thought that the old Internet Explorer was the reason, but I tried it in the online Outlook website in Internet Explorer and it worked great. The most annoying issue is that whenever I try to open the debugger from Outlook, it won't work / won't open. I don't know why.
Do you know of any possible reasons that might explain the plugin not working in Outlook but working in the web version? Please help
I'm using Microsoft Teams desktop app in Windows 10.
I created a new Channel with a Web site Tab.
Unfortunately, I'm not able to surf in the Tab because a message is pop up saying:
"Outdated browser version"
"Please update your Chrome version to 86 or higher"
I reviewed the logs and the user agent is pointing to an old Chrome version:
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Teams/1.4.00.4167 Chrome/80.0.3987.165 Electron/8.5.1 Safari/537.36"
On the contrary, if I open Microsoft Team web version I'm able to display the Tab and surf on it without any problem since my web browser is higher than 86.
How can I upgrade this feature. I need Microsoft Teams to use a higher version of Chrome in order to support the web page in the Tab.
Here are my apps versions:
Microsoft Teams: 1.4.00.4167
Chrome: 88.0.4324.190
The problem:
I have a feature for a Microsoft Outlook web add-in which works fine in Office 365 Outlook, but when I test the same feature on Outlook for Mac or Outlook for Windows, the same feature doesn't work. The web add-in still installs fine on Outlook for Mac, it's just that there is a discrepancy between the behavior I am seeing on Office 365 Outlook and Outlook for Mac (this is also true when testing on Outlook for Windows, which has the same behavior as the Mac version).
What I've tried (Mac): I've tried running defaults write NSGlobalDomain WebKitDeveloperExtras -bool true as suggested from this answer and defaults write com.microsoft.Outlook OfficeWebAddinDeveloperExtras -bool true as suggested here and have an option to View Source which opens the HTML source in what appears to be a TextEdit window, but I'm still unable to inspect element in order to see any errors.
What I've tried (Windows):
I've tried using the VSCode Debugger Extension for Office Add-Ins to try to attach the debugger to Outlook for Windows, but keep running into this 'Error processing attach' error.
Additional Notes:
On Mac, I'm running Microsoft Outlook for Mac version 16.43 on MacOS Catalina version 10.15.6 and on Windows I'm running Outlook on Windows 10 Pro version 1909 inside a VM.
My understanding is that while debugging web add-ins for Word, Excel, and PowerPoint are all pretty well supported, debugging add-ins for Outlook on Mac or Windows is somewhat limited at the moment. Has anyone had success in debugging Outlook web add-ins running on Outlook for Mac and/or Windows?
For Outlook for Mac, we think this is specific to the Mac App Store build of Office, which currently doesn't support those flags. To workaround this, you will need to get a non App Store build. You can get one by signing up for the developer program and getting a tenant: https://aka.ms/o365devprogram. (similar issue: https://github.com/OfficeDev/office-js/issues/506)
For Outlook for Windows, we suggest attaching a debugger. Instructions for how to attach a debugger can be found here. Note that there is a different debugger for add-ins that run in Edge and IE.
We have an add-in that works fine on Outlook for mac but not on windows for IMAP (Gmail) accounts.
Is the setup different to how the IMAP is configured on MAC and Windows?
Mac Version - 16.41 (20091302)
Win Version - 16.0.13127.20402
This is an issue because a lot of our users are unable to use the add-in when they have multiple accounts in Outlook on windows (of which most are IMAP - Gmail)
I would have thought it would be other way around where Add-ins would be available on Windows and not on Mac since a lot other things are not supported on Mac within outlook.
Are there settings that can be changed to make them available on windows or of anyone knows about this being available in the future?
----------------- UPDATE --------------------
Mac Version - 16.42 (20101102)
So, this morning 19th Oct, 2020. I got an Outlook Update for mac and as per the screenshot below, you can clearly see that I am using a Google Account (IMAP) and the add-ins are availanle.
Outlook Web Add-Ins are only supported on Outlook accounts connected to an Exchange server. Further documentation here : https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/add-in-requirements