Firefox iOS is not marked as a modern brower

[ToyboxZach]

Firefox ios gets parsed as firefoxIOS which is not in any of the aliases or anything in the modern browser:

const browser = WebAppInternals.identifyBrowser(
  "Mozilla/5.0 (iPhone; CPU iPhone OS 17_4_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) FxiOS/125.3  Mobile/15E148 Safari/605.1.15"
);
console.log("Minimum browser versions", browser, isModern(browser));

This is something that does keep happening when a new browser starts existing or becomes more popular, is there a good way to get notified or log when some completely unexpected browser starts using our site?

For some other reason our legacy bundle is broken, so this lead to a subset of users being completely broken.

[rj-david]

Unfortunately, meteor is using a 6-year-old unmaintained package: https://www.npmjs.com/package/useragent

This means that the database of existing user agents is not updated during the last 6 years :(

There is a fork that pulls from an updated database
Fork: https://www.npmjs.com/package/useragent-ng
Updated database of useragents: https://github.com/ua-parser/uap-core

I have not looked at the families of useragents but this might require a change in modern-browsers package to handle new browsers

[ToyboxZach]

The package is actually able to identify it as firefoxIos but meteor just doesn't map it to anything so it's always legacy.

[rj-david]

In that case, seems the fix should be adding an alias to the correct family of useragents

[ToyboxZach]

Yeah I'm able to fix it locally with this on my server:

setMinimumBrowserVersions(
    {
      "mobileSafariUI/WKWebView": 8,
      appleMail: 500,
      ios: 8,
      firefoxIOS: 100,
    },
    "classes"
  );

This is not the first time I've had problems with a new browser being marked as legacy, so I feel like this experience is somewhat lacking as a developer.

At this point, a new browser is more likely than not modern, so it's weird that be default every browser is defaulting to legacy instead of assuming modern. I also just happen to never want to server a legacy bundle anymore, but couldn't figure out how to do that. At a minimum it would be helpful to be able to log any browsers types that we don't have a mapping for, so I can react a bit quicker than I did with this one.

[KoenLav]

#12177