You will still be able to access it.
1 Like
Just chiming in with a quick update…
As Chrome 93 begins to roll out it appears as though the impending change that would have blocked traffic between Tablo DVRs and Chrome browsers has been delayed to Chrome 94 (currently in beta) or beyond.
At this time it’s unclear when the change will actually be implemented but we will do our best to keep you all informed.
In the meantime, we still recommend that Windows users download and use the Tablo Windows 10 app moving forward.
Hi folks - Another quick update…
We have removed the Chrome banner warning message for now.
But the reality remains that we don’t really know when browser support for my.tablotv.com could fail.
Our goal is still to complete the full update of the Windows 10 app before this happens so all of your favorite features and screens remain accessible.
As we move forward, we’ll do our best to keep on top these browser changes and keep you apprised.
If you’d like to follow along with more detailed updates, there’s a new section at the bottom of the Knowledge Base article on this subject:
Some info on the Google Chrome v.100
Hopefully the Tablo web app is/will be ready for this.
Seriously, checking specifically for version by length in a string? It’s got to be one of the original world wide web, sites.
Wow, if tablo web app can’t correctly find appVersion yet create all the apps used to access and operate the tablo… LOL
You might have a piece of software that is dependent of a minimum or a range of browser versions for allowed installation. And since these versions are controlled by the various platform specific packaging software many have stuck with some form of the two digit decimal major, minor, update numbering system invented in the late1960’s to early 1970’s.
Of course some of us wanted the version numbering system to be in hex but since there were still octal systems that didn’t fly.
Exchange says hold my beer…
1 Like
You mean converting an unsigned 32 bit number into a signed 32 bit container won’t cause it to properly enter a black hole and go back in time.
Isn’t that more a developer-specific bug?
These errors are caused by Microsoft Exchange checking the version of the FIP-FS antivirus scanning engine and attempting to store the date in a signed int32 variable.
However, this variable can store only a maximum value of 2,147,483,647, which is less than the new date value of 2,201,010,001 for January 1st, 2022, at midnight.
Knowing their own variable had limitations… and explicitly giving it a value outside it’s limits? Releasing it without testing?
Never said it wasn’t. In both cases it is a code bug.
1 Like
Just an old school assignment issue. many languages require that those types of assignments require a cast assigment. And there have been tools for years that scan source code looking for those assignment issues.
Of course results would have been completely different on an Itanium processor.
That chrome policy of restricting communication between the tablo & chrome hurts. If tablo 4th gen could be run in a chrome tab that may have been the answer of using 4th gen tablo to cast a show from a laptop or pc to chromecast.