Open coreyroth opened 3 years ago
This is also problematic as the chromium UserAgent reported by windows 11 actually identifies as Windows 10. And by default the new secure client headers do not send the OS version. Also on the client the getHighEntrophyValues() API (the only way to get the reported OS version -- which is v14 on Windows 11) is asynchronous, so unless you hold up the PageView event from being reported (which will affect the reported time) this information would also not be included.
This Issue will be closed in 30 days. Please remove the "Stale" label or comment to avoid closure with no action.
This Issue will be closed in 30 days. Please remove the "Stale" label or comment to avoid closure with no action.
We would also appreciate the ability to see the distribution of Windows 10 and Windows 11 customers. We are still seeing this issue when using these versions:
This Issue will be closed in 30 days. Please remove the "Stale" label or comment to avoid closure with no action.
I don't know if this is by design of either Windows / Edge and / or the Application Insights SDK. However, I noticed that the client_OS field in pageViews shows Windows 10 instead of Windows 11.
I am guessing the SDK uses either navigator.appVersion, navigator.userAgent, or navigator.userAgentData to determine the value for this column. When examining that string I can see the difficulty. However, I wanted to raise this as I know customers have an interest in seeing the breakdown between Windows 10 and Windows 11.
Steps to Reproduce Log a pageView using the SDK on a Windows 11 device.
Expected behavior client_OS shows Windows 11