Frozen SamsungBrowser about yauaa HOT 9 CLOSED

Yes, you are right. The Samsung browser has changed their behavior with the latest release.

from yauaa.

Fixed.
https://github.com/nielsbasjes/yauaa/blob/main/analyzer/src/main/resources/UserAgents/Samsung.yaml#L2301-L2410

from yauaa.

hey @nielsbasjes ，this issue is not only a bug report, but also a feature requirement :)

Is there any method or api to known it's a frozen useragent?

from yauaa.

I'll have a look.
Do realize that I already in know of at least 3 different ways of reducing the ua info.

from yauaa.

Q: What is the usecase you would like to know this for? Im thinking perhaps simply looking at the '??' is the best way?

from yauaa.

My usecase is to stat the real mobile os version, so i need to exclude the frozen ua, looking at '??' can do that, but just this way make me uncomfortable

from yauaa.

Ok, understood.
I'll investigate what is the most reliable way to determine this.
Right now your check for '??' seems like the best option.

from yauaa.

I double checked.

Simply reporting if the UA was frozen is not an accurate answer to your question. Looking at the version and filtering it out if it is '??' is actually the correct way of doing what you are looking for.

An example is that when ClientHints are available then the UA was frozen and still the actual OS version is available.
https://github.com/nielsbasjes/yauaa/blob/main/analyzer/src/main/resources/UserAgents/Samsung.yaml#L2364-L2384

from yauaa.

I have released a new version with the Samsung fix in it.

from yauaa.