If you’re having problems with 3.1.x and Edge Mobile

…then it can save you some time to know that there’s a bug in meteor likely introduced when changing user agent parser to useragent-ng which emits “Edge Mobile” instead of “Edge” for iOS and Android Edge versions.

That family (encoded as edgeMobile) has no “modern-browser” entries in the meteor packages so Edge Mobile receives the “legacy browser bundle” instead of the normal “modern” bundle (modern is relative - here means that it’s < 9 years old).

A workaround is available upon request.

Just kidding - it’s in the issue:

I would really like to disable the legacy bundle feature and always serve web.browser (”modern”).

Is that possible?

2 Likes

Did you try to use this package to set this browser as modern? meteor/packages/modern-browsers at master · meteor/meteor · GitHub

Example

import { setMinimumBrowserVersions } from 'meteor/modern-browsers'
setMinimumBrowserVersions({
  facebook: 325
}, 'minimum versions for ECMAScript 2015 classes')

1 Like