Skip to content

Added support for Windows IoT 10.0 devices #5706

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 3, 2018

Conversation

nickurt
Copy link
Contributor

@nickurt nickurt commented Feb 3, 2018

The UserAgent for Windows IoT 10.0 devices recently changed from

Mozilla/5.0 (Windows Phone 10.0; Android 6.0.1; WebView/3.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Mobile Safari/537.36 Edge/16.16299

to

Mozilla/5.0 (Windows IoT 10.0; Android 6.0.1; WebView/3.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Mobile Safari/537.36 Edge/17.17083

@sgiehl sgiehl merged commit 51a7d8d into matomo-org:master Feb 3, 2018
@nickurt nickurt deleted the patch-1 branch February 3, 2018 16:11
@Findus23
Copy link
Collaborator

Findus23 commented Feb 4, 2018

Added icon in matomo-org/matomo-icons@588dff8
As what kind of Device type will an IoT device be detected?

@sgiehl
Copy link
Member

sgiehl commented Feb 4, 2018

@Findus23 currently it won't have any I guess, as the user agent doesn't contain a device fragment

@nickurt
Copy link
Contributor Author

nickurt commented Feb 4, 2018

@Findus23 @sgiehl I had a little bit the same feelings when I added them actually.

You can see Windows IoT Core as a RPI/MBM/IntelJoule-device with no display, but you can also use it with an display and interact with Cortana UWP and other UWP-apps.

I don't know in what DeviceType a Windows Embeded Compact-device is atm, but you can see it rougly as the successor to it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants