Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Ios_chr ua detection is not correct

See original GitHub issue

A bug report

What

CriOS/92.0.4515.90Supported features promise.any ios_saf/11.0.0 Does not support feature promise.any

Details

device： iPhone 7P
OS: IOS 14.8
chrome： 92.0.4515.90

const polyfillLibrary = require('polyfill-library');
// ios_chr
const ua = 'Mozilla/5.0 (iPhone; CPU iPhone OS 14_8 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/92.0.4515.90 Mobile/15E148 Safari/604.1';
// 手机 ios_saf
// const ua = 'Mozilla/5.0 (iPhone; CPU iPhone OS 14_8_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.1.2 Mobile/15E148 Safari/604.1';
console.log(polyfillLibrary.normalizeUserAgent(ua))
 // ios_chr : ios_saf/11.0.0
//  ios_saf : ios_saf/14.1.0

Ios Safari and WebKit kernel information

https://raw.githubusercontent.com/mdn/browser-compat-data/main/browsers/safari_ios.json

Judging UA by ios Safari and ios Chrome by ‘Safari/604.1’ is inaccurate The actual UA displayed does not match the engine_version of the version release list

by the way: macos safari ua: “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.1 Safari/605.1.15”

{
  "14.1": {
  "release_date": "2021-04-26",
  "release_notes": "https://developer.apple.com/documentation/safari-release-notes/safari-14_1-release-notes",
  "status": "retired",
  "engine": "WebKit",
  "engine_version": "611.1.21"
}
}

CriOS/ X.X.X is removed from iOS_CHR, and the webKit version is converted to iOS_SAF, which will add many polyfills，Is that unreasonable?

Issue Analytics

State:
Created 2 years ago
Comments:6

Top GitHub Comments

1reaction

romainmenkecommented, Jul 31, 2022

@zloirock thank you 😃

I really don’t understand how/why it is so hard to expose reliable and precise engine information.

1reaction

romainmenkecommented, Jul 31, 2022

Filed bugs with firefox and chromium to see what the response will be :

chromium bug : https://bugs.chromium.org/p/chromium/issues/detail?id=1348792 firefox bug : https://github.com/mozilla-mobile/firefox-ios/issues/11464

Top Results From Across the Web

A Practical Guide to Urine Drug Monitoring - PMC - NCBI

Urine drug monitoring (UDM) is an important tool to screen adherence and identify possible misuse and abuse in patients on opioid therapy.1 Various ......

Clinical Drug Testing in Primary Care - SAMHSA Publications

Drug test results may provide more accurate information than patient self-report. Although drug testing can be a useful tool for making clinical decisions,...

DOT Rule 49 CFR Part 40 Section 40.203

Subpart I—Problems in Drug Tests§ 40.203 What problems cause a drug test to be cancelled unless they are corrected?(a) As the MRO, when...

SUBMISSION TO OHCHR STUDY ON YOUTH AND HUMAN ...

The use of sniffer dogs and random drug testing in schools not only raise similar ethical concerns, but also have not been proven...

Drug Testing | Choose the Right Test - ARUP Consult

Opiates. Most available IAs do not readily detect semisynthetic opioids (oxycodone, hydrocodone, and their metabolites) and synthetic opioids (eg, fentanyl, ...