-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
Google Search App on Iphone is not detected properly #960
Comments
Thank you, I will have look later today. |
@wangkanai thanks. It looks like google chrome on IOS is also identified wrongly Looks like your current logic parses Safari/{XXXX} first which probably should be the last check. |
Are you sure this is Google Chrome? Because I don't see Chrome in the UA. Also, CriOS is something new that I have never seen before. Edit: After researching CriOS == Chrome iOS |
A new browser type, Google Search App, has been added to the Browser enumeration in the Detection library. Corresponding unit tests for the Google Search App have also been added to ensure proper identification and version resolution. Ref: #960
Done! and release |
@wangkanai thanks for a quick fix, works as expected now. There is another thing which I don't remember to work properly - android version is always 0.0 This is the user agent from Samsung Galaxy S24 Ultra with android 14 but in my logs I see a bunch of customers having the same UA. Reading this article I see that google does it intentionally and moved useful information into user agent client hints since 2022... Is it possible to fix it as well? Thanks |
Google Search App on Iphone / Ipad is not detected properly
The UserAgent I receive on backend is
UA:Mozilla/5.0 (iPhone; CPU iPhone OS 17_4 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) GSA/312.2.624279232 Mobile/15E148 Safari/604.1
Wangkanai.Detection.Services.DetectionService v 8.12 detects it as Safari 604.1, iOS 17.4, Mobile
whatismybrowser.com detects it properly as Google Search App 312.2 which I assume is possible through GSA/312.2 part
Can you please fix it so the browser is identified as other?
The text was updated successfully, but these errors were encountered: