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
Related
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.
I have seen similar questions in SO but they don't exactly point to the same problem I am facing.
I have two different desktops with same OS (Windows 8) and same version of IE (11.0.9600).
I am trying to connect to the same URL from these two desktops.
However, I notice that two different user-agent values are being submitted from these two IEs.
User-Agent Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; Touch; rv:11.0) like Gecko
and
User-Agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.3; WOW64; Trident/7.0; Touch; .NET4.0E; .NET4.0C; .NET CLR 3.5.30729; .NET CLR 2.0.50727; .NET CLR 3.0.30729; InfoPath.3; Tablet PC 2.0)
Can someone please help me understand how do I figure out the reason for this?
This issue has implication for me as the portal I am trying to access does not allow the first user-agent value and shows "unsupported browser" message.
Look at the User-Agent, in the second you have "compatible".
This compatible mode on F12 and its run with Explorer 10 user agent.
You are in the compatibility mode in the second instance.As IE is installed along with your windows, it may have been configured automatically in that mode.
Searched on Google but couldn't find anything useful.
Programming some statistics about User Agents and came across this one:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; MRA 5.8 (build 4157); .NET CLR 2.0.50727; AskTbPTV/5.11.3.15590)
What does 'AskTbPTV' in HTTP User Agent stand for?
Ask.com toolbar http://apnstatic.ask.com/static/toolbar/everest/download/index.html?source=sp wich modify user agent string.
I've got a curious problem with a friend's computer. Although I've verified he's using Internet Explorer 8.0.6001.18702 on Windows XP (up to date with all things from Microsoft Update).
However, here is the user agent string it reports:
Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C)
This is bizarre for a number of reasons:
IE8 is reporting that it's IE9. The Trident/4.0 definitely verifies that it's IE8. This is referenced by the official Microsoft documentation on the user agent string: http://msdn.microsoft.com/en-us/library/windows/desktop/ms537503(v=vs.85).aspx
I've only ever seen Mozilla/5.0 in the user agent string for actual versions of IE9.
I'm stumped. We've done a reset of IE (KB923737 at http://support.microsoft.com/kb/923737), I've disabled all extensions/addons inside IE, and there doesn't seem to be anything installed that would be purposefully altering the user agent string. I've also dug into the registry to see if the user agent string is being spoofed, and it is at the default (unaltered).
Anyone have any ideas of what I should look at or try next...or what might be responsible for IE8's apparent identity crisis?
We had a customer with the same issue. Also stumped. We changed to using TRIDENT as well as the MSIE number to accurately detect what they were using.
If they are using Trident 4, it is either IE 8 (or IE 7 because of compat mode) but nothing higher. Same for other versions of IE as well. Trident 5 can't be higher than IE 9, etc.
When I asked this question I accepted the answere because it made sense and the documentation pointed was right.
Testing a machine with IE6 against other one with IE7 with the same compiled executable using TWebBrowser the behaviour was indeed as pointed in the answere.
Now I put the answere in doubt again, in a machine with IE8 that same executable is being identified as IE7 by the server. I wrote a simple rails app that pirnts the user agent and it is clear. In the same machine if I access this rails app in IE it prints:
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; GTB6.5; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.30729; InfoPath.2; .NET CLR 3.0.30729)
When I access using that executable:
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; Trident/4.0; GTB6.5; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.30729; InfoPath.2; .NET CLR 3.0.30729)
Furthermore, with a little help from my friend Process Monitor I realized that the classid called to instantiate the TWebBrowser is {8856F961-340A-11D0-A96B-00C04FD705A2} wich in windows registry has the name "Microsoft Web Browser" and points to ieframe.dll.
Now the things get a little more strange. If I go to system32/ieframe.dll and check the version... 8.0.
I´m really confused. The question is: When I use TWebBrowser, wich version of ie will be used, indeed?
Thanks.
It's using IE8, but in IE7 compatibility mode. The IE team blogged about this back in March 2009, where they also described how you can get IE8 rendering instead of the IE7 default.
I haven't seen anything about how IE9 will behave here, so I can't say if you'll need a different value to use IE9 rendering, or if there's some other value which simply means "newest" and gets IE8 rendering as well.
Maybe TWebBrowser saves the Useragent it had at the time of creation in ControlData property? Try deleting and re-adding the control to the form on a computer with IE8.0 installed.
At any case, those User agent strings looks oddly similar. It's probably the same IE8.0 engine, no matter what it prints.