We have an app that several users use in fullscreen mode on Samsung and LG Smart TV browsers or through Amazon Fire Sticks and Tablets.
Previously we ran Meteor 1.10.2 and the app ran well on the above browsers. But now 2.7.1 is broken on these, specifically with an Iron Router no route found error message, which usually happens in development when something else is broken and/or not compiling correctly.
In the Meteor change log I remember reading about dropped browser support for IE9 (or something - couldnāt find it upon searching) so Iām wondering if that is causing the problem.
I have specs on the models, software, and browser versions. The LG TV uses webOS TV 5.3.2-2205. I am going to try to see if thereās any emulators or versions that can be downloaded to a computer and tested.
Weāre on Blaze 2.6.0. I will update to 2.6.1-rc.1 and report back.
A few new findings to add:
On the LG Smart TV it uses webOS TV 5.3.2-2205, which on the LG website states they use Chromium 68 as a browser. I went on lambdatest.com and tested the app in Chrome 68 and it indeed breaks with an error:
Hard to get much more out of it than that as itās a minified production app. So I downloaded an old Chromium 68 build to run locally in development and I can see much more errors, including the above one first, but also several with Uncaught ReferenceError: meteorInstall is not defined.
I was able to get the Meteor example app tic-toc-toe running in 2.7.1 in both modern Chrome and Chromium 68. So itās probably not a Meteor issue per se. Upon researching, I realize Iāve had issues like this before and itās usually an npm or meteor package causing the issue.
I thought for sure it would be @babel/runtime, jquery, bcrypt, or meteor-node-stubs but I tried updating them all and/or changing them back to the version I ran in 1.10.2 but nothing worked. I even used the versions of those packages that tic-toc-toe used (when applicable) but that didnāt work.
Then I saw that my new 2.7.1 was missing es5-shim (I did a lot of package shuffling in the upgrade). I thought for sure that was it. Nope.
BTW, whatās the current status for Meteor 2.7.1 on npm versions of:
@babel/runtime
bcrypt
meteor-node-stubs
In past versions of Meteor updates, these has specific versions they had to be set at.
I may have to start the arduous process of rebuilding the app from a fresh meteor install, adding package by package.
Figured it out, yep, bad npm package. We use screenfull for full-screening and their latest version of the package is a pure ESM package which I admittedly donāt know much about, but I did read all their info upon updating the package. It sounded like Meteor took care of this, but perhaps the old way of importing it:
import screenfull from 'screenfull';
Needs an update per the ESM rules? At least for old browsers? Anyway, per their instructions, rolling back to the the prior stable version made it all work.
For anyone who wants the know the process for identifying the bad npm package, hereās what I did.
Remove all npm packages from package.js except for the standard ones of a default Meteor project (@babel/runtime, jquery, meteor-node-stubs).
Add only the npm packages needed to build the project. Youāll see lots of errors, but eventually your project will build once all the server npm packages are added. Any client npm packages will error out once loading the app in the browser.
At this point I got lucky and both the modern Chrome and Chromium 68 browsers displayed the same errors (e.g. the missing npm client packages).
At this point itās just adding back the remaining npm packages one by one (or in chunks to go faster) and waiting for the Chromium 68 console to spit out the above mystery breakage.
Voilaā¦ found the errant package. Rolled back to their safe version.
Lastly, whatās the status on needing bcrypt as an npm package?
Thanks for sharing how you could figure out the root cause of the problem.
About IE, Meteor should continue working on it. I believe @zodern was able to fix the issue on this PR.
We should add it soon in the next beta version.
