Closed atom-box closed 2 months ago
This issue seems to have started on March 20 / 21. Here is the phablet detection rate over time:
(these screenshots are from a totally unrelated user, with a different Matomo server, than the screenshots in my first message, above)
Maybe this is good easy first-issue for a contributor. @brototyp is there a way to flag this as "easy starter issue"?
Hey @atom-box, thanks for reporting this. I have the suspicion, that this is an issue serverside. What do you use as a backend? Your own hosted Matomo instance? Is it possible, that you updated that instance in March?
Closing this for now. Please feel free to re-open the ticket if you think it still exists.
@brototyp : Why was this closed? The problem still exists!
@PeteTrombone I closed this issue since it is stale. I cannot reproduce it from my side and nobody responded to debug together with me. So the only assumption left for me was that it probably is resolved.
@brototyp as I said, the problem still exists. Here is the proof:
@atom-box maybe you have some more examples that the problem has not yet been solved?
I believe you, that it still exists. That fact alone does not help to debug it though. Do you have any information to help narrow down the issue?
What do you use as a backend? Your own hosted Matomo instance or the Matomo-hosted one?
Can you correlate the appearance of this issue with an update of the backend or the SDK?
@Findus23 Do you think this issue might be related to any changes in the https://github.com/matomo-org/device-detector ?
The iOS SDK seems to over-attribute the device type as phablet.
Notice the very different rates for phablet data from three different sources:
Using the iOS SDK for an app 88% phablet
Using the Android SDK for the Android version of the same app 9% phablet
Using Matomo for my desktop website 4% phablet