matomo-org / matomo-org/device-detector

Guidance needed on how to handle deviceType == null for custom streaming/podcast/gaming apps

Open
#7,992 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
PHP
Stars
3.5k
Forks
513
Avg merge
1d 21h
Merged PRs (30d)
11

Description

Hello,
I haven't posted before and not an engineer, so please let me know if this is okay to post here.
My company recently installed this library to replace an outdated device detection solution. While generally way better, we are seeing a lot of deviceType = = null for a lot of what appear to be custom apps for audio streaming and podcasting or mobile games.

I'm looking to understand the reasoning. Are the user agents not properly formatted? Are they missing information? Do they simply need to be added to the device-detector?

Here are some example UAs we are seeing result in deviceType==null

NYTimes-iOS/11.8.0 CFNetwork/1568.200.51 Darwin/24.1.0
Word%20Search/94 CFNetwork/3826.400.120 Darwin/24.3.0
MonsterBattleSeries/7 CFNetwork/1496.0.7 Darwin/23.5.0
GalacticDorm/12 CFNetwork/1335.0.3 Darwin/21.6.0
SoundCloud/1247108 CFNetwork/1494.0.7 Darwin/23.4.0
Radioplayer/8.0.4.162 ios/18.3 AVPlayer/5.0.0 (Swift) Radioplayer Worldwide Ltd
Radio%20Clyde/3972 CFNetwork/1568.200.51 Darwin/24.1.0
Absolute/3972 CFNetwork/1335.0.3.4 Darwin/21.6.0
Hits%20Radio%20South%20Wales/3967 CFNetwork/1568.200.51 Darwin/24.1.0

Please let me know if someone would be able to help guide me on the best next steps for cases like these.

I appreciate your help!

thanks,
Ryan

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the listed user-agent examples and the library's deviceType detection behavior, starting with the relevant detection entry point. Done would be a documented explanation of the null results or a clearly scoped detection change with tests, but the issue names no source file or test.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.