Feature Request: Error Page when Channel fails to load

[ocelotsloth]

As I mentioned in #18, if the given URL doesn't load/exist/resolve, all we get for feedback is a blank white screen. A quick JS script to detect this failure mode and change the page to show a simple error message explaining why the channel didn't load would be super helpful for diagnostics.

I'll write something next week and push it up.

[Brekmister]

I did find other things that can be diagnosed as well such as bad CSS or JS...

Ok, I totally knew I was doing...I just made some typos and used Firefox Developer tools to diagnose it. I didn't break anything, I SWEAR

Or you know, I was just screwing around :)

[ocelotsloth]

What about adding a Development mode that just prints all alerts and errors to the screen as alerts on the physical chrome casts?

This would allow us to see when something isn't working in the testing phase, but also see the exact error message just in case it's different from what we get in testing browsers. Unless somebody knows how to get the developer tools working on a Chromecast.

This could be combined with a more generic page that shows when in production mode that just shows a configurable logo along with an "Oops, looks like something went wrong."

[Brekmister]

Also diagnosed in #1

[ocelotsloth]

^ Could even be combined with an api on the server that let's the chrome casts report back errors to the server to get logged in the log files.

That could be a /log/ endpoint that just takes some text and dumps it as a log message.

[Brekmister]

Actually, it's a better idea to make a log/dashboard page and use a channel or template to go to it.

If we are talking about developer mode.

Quite honestly, I don't know if Iframe throws an error in JS when such thing happens. Or how to catch it.

[Brekmister]

Communicating with the Chromecast is a piece of cake, the issue is whether the Chromecast can report such errors.

…

On Oct 15, 2017 12:35 AM, "Mark Stenglein" ***@***.***> wrote: ^ Could even be combined with an api on the server that let's the chrome casts report back errors to the server to get logged in the log files. That could be a /log/ endpoint that just takes some text and dumps it as a log message. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#19 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIAC9v4N4tIcr9mkqWo_mhyQfEffp63oks5ssZmWgaJpZM4P5ocD> .

[ocelotsloth]

Something like this should do the trick: https://stackoverflow.com/a/8000059

Just wrap the console.warn/err/etc methods so that they also do an http call to the server to report the contents of any error that is posted.

[Brekmister]

I'll experiment this a little more...I'll give you an update with results.

…

On Oct 15, 2017 1:06 AM, "Mark Stenglein" ***@***.***> wrote: Something like this should do the trick: https://stackoverflow.com/a/ 8000059 Just wrap the console.warn/err/etc methods so that they also do an http call to the server to report the contents of any error that is posted. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#19 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIAC9n2OZLdI09dcXetzrvratPDZqq94ks5ssaEBgaJpZM4P5ocD> .

[superhawk610]

Chromecasts actually offer a built-in debugger via Google Chrome, accessible at chrome://inspect. This will list all Chromecast receivers on the LAN and allow access to their layout and console in real time.

I do think logging would be a very useful feature, for debugging in the short-term and maintenance in the long-term. I'll open a new branch for this and try to get some work done for it when I get a chance.

[Brekmister]

Just wanted to let you guys what I do right now for testing:

Just click the preview link on the device, it will render exactly the same page the chromecast is running on, including my rotation feature. If there is an error, just open up developer tools to see what's wrong.