Skip to main content

Troubleshooting

Supporting old browsers​

Unfortunately, many signage devices run ancient versions of browsers. You need to ensure that your custom app's JavaScript and CSS code is supported by the device you plan to deploy your content on.

Techniques for supporting old browsers​

  1. Use Babeljs.io to compile your code to target older browsers.
  2. Use our template, which targets an old browser version out of the box.
  3. Test. Sometimes you have to run it on a real device and see what happens.

Minimum browser versions per device​

DeviceMinimum browser version
Android 5Chromium 37
Android 5.1Chromium 39
Android 6Chromium 44
Android 7Chromium 51
Android 7.1Chromium 52
Android 8Chromium 58
Android 8.1Chromium 61
Android 9Chromium 66
Android 10Chromium 74
Android 11Chromium 83
Android 12Chromium 91
BrightSign 7.xChromium 45
BrightSign 8.1.xChromium 69
BrightSign 8.2.xChromium 69
BrightSign 8.3.xChromium 69
BrightSign 8.4.xChromium 69
BrightSign 8.5.xChromium 87
BrightSign 9.0.xChromium 87
Tizen 3.0Chromium 47
Tizen 4.0Chromium 56
webOS 4.0Chromium 53
webOS 4.1Chromium 53
webOS 6.0Chromium 79

Logging​

Once you have deployed your custom app to a real device, it can be hard to know why things might be going wrong. The first place you will want to look is the browser logs.

Historically speaking, it has been hard for Fusion Signage developers themselves to get logs off devices out in the world. We are working on building a logging library into our SDK to simplify remote logging, but in the interim you may find a tool like Sentry to be useful for remotely investigating errors.

Be sure to transpile the Sentry library itself so that it works for your target device, as Sentry also uses fairly modern JavaScript features. Our example template will take care of this for you.