Problems if Chrome in blacklist Android 8.1
There are definitely complications in Blacklisting the Chrome application in Android 8.1. The SOTI Lockdown utilizes the System WebView to render the HTML lockdown template. In newer Android versions the System WebView implementation is Chrome, so by blacklisting it you're also blacklisting the rendering engine for the lockdown itself. When Chrome is blacklisted the default System WebView takes over so the lockdown can still run, but via the System WebView. The challenge is then if you enter Admin mode on the device the Blacklist will be temporarily disable which will in effect re-enable Chrome and then change the System WebView to Chrome. This can in turn cause the agent and lockdown to refresh itself which then re-enables the blacklist, thereby disabling Chrome again! Basically you can end up in a trap where you can't exit the lockdown for any longer than a few seconds.
It should be technically possible to blacklist any app and also configure the lockdown mode on device. However, if you wish to not have the Chrome browser in lockdown, do not add it in lockdown configuration.
However, for any reason if it is mandatory to blacklist the Chrome app, please contact Support team and someone will assist you further as we might have to take a look at the the logs.
SOTI Technical Support | SOTI Inc. | 1.905.624.9828 | firstname.lastname@example.org