-
Notifications
You must be signed in to change notification settings - Fork 166
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
Device Detection for Mac broken since 7.3 #361
Comments
Hi @lrrrs, thanks for reporting this issue. I just had a look at it. Apparently the old mechanism did report a macOS version that could be recognized, but it sometimes was wrong. This for example is how the old version on 11.0.1 looks like (apparently webkit reports this wrong / differently). For the issue you reported: I think the issue is the This is the PR: #362 |
I guess Apple uses |
Yes, since 2016 it's called |
I'm trying to do a quick temporary fix in the device detector. Would this be the right place (It does not seem to change anything):
Add this rule:
Testing it via Matomo > Diagnostics > Device Detection seems to work fine: |
I recently updated the Matomo SDK in my app to the latest version (7.3). Looking at the
operation system statistics
, more and more genericMac
systems w/o a detected version number popped up. I'm realizing now that it's completely broken since this change #353.A generated User-Agent from my Mac app looks like this:
AppName/1.0 x86_64 macOS/11.0.1 MatomoTrackerSDK/7.3 Darwin/20.1.0
And trying it out with the device detector demo confirms, that it's broken.
The old
User-Agent
generated from an earlier SDK version obviously works (But detects the OS wrong, it's 11.0 or 10.16 and not 10.15.6):Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) MatomoTracker SDK URLSessionDispatcher
The question is: Should this be fixed in the client iOS/Mac SDK or on the server side? Help? 😊
The text was updated successfully, but these errors were encountered: