On the 1st June 2018 we were made aware that a handful of customers were unable to register new devices to their remote management accounts. After testing registration from a number of different devices we found that the issue was only present on Android 4.4 or lower.

The solution is to upgrade Kiosk Browser to v2.6.5 (build 210) as soon as possible. You can find the latest APK here. We are holding off from releasing via Google Play for a few days.

Impact
Devices running Android 4.4 or lower will no longer receive profile updates. You will not be able to register new devices running 4.4 or lower.

Reason
Our mobile backend which takes care of device registration and profile updates is hosted on Microsoft Azure (Mobile Services). Microsoft Azure decided that all web apps will now be forced to TLS 1.2 by default when connecting to an SNI-SSL binding if the hostname is not included in the CLIENT HELLO message. The Azure Mobile library for Android does not include the hostname and therefore defaults to TLS 1.2.
Android 4.4 and lower does not support TLS 1.2 natively and needs to connect using TLS 1.0 but these requests fail.

Solution 03/06/2018
We have been working hard over the weekend to come up with a solution to the problem which involves moving our mobile backend onto our core server. However no solution was found to make existing devices function fully without a software update..
The solution is to upgrade Kiosk Browser to v2.6.5 (build 210) as soon as possible. You can find the latest APK here. We are holding off from releasing via Google Play for a few days. If you are running a custom build of Kiosk Browser you will need to contact us for the latest version.

Apologies
This was a completely unforeseen problem, we've worked tirelessly over the last two days to ensure such an issue never occurs in the future.
Was this article helpful?
Thank you!