KB: XML Import & Export
Deprecated in v2.8.8 or higher.
XML Import is incredibly useful if you wish to bulk provision a large number of devices where the configuration of each device needs to be identical. Note Remote Management can also configure large numbers of devices via configuration profiles but it has a number of requirements such as Google Play services and an active internet connection.
Do not use XML files if you are using remote management (they are not imported automatically from v2.0.36 onwards).
Please note that you may find this feature no longer works in Android 9.0 and later due to SDK security changes, if you find this feature no longer works then we would recommend switching to an automatic configuration JSON hosted on your own webserver, which you can find information on here: Automatic Configuration JSON
You can create an XML file from scratch but it's far easier to configure 1 device with the settings you need and Export the XML file via Settings > Admin > Export to XML. This will create a file called kioskbrowserconfig.xml in the root of the device' default storage.
Kiosk Browser will automatically Import settings from kioskbrowserconfig.xml when stored in the root of the device' default storage. Please note this will only happen on first launch and not once Kiosk Browser is loaded into memory. So for testing purposes you can either reboot the device or force stop Kiosk Browser via Settings > Apps.
If kioskbrowserconfig.xml remains stored in the same location, each time Kiosk Browser is first launched it will be re-imported.
Deleting XML File on Import
If you only want the configuration file to be imported once, you can specify a delete command within the XML file so that kioskbrowserconfig.xml is automatically deleted once a successful import has occurred. Just modify the existing preference key in the XML file as per below:
XML Import is incredibly useful if you wish to bulk provision a large number of devices where the configuration of each device needs to be identical. Note Remote Management can also configure large numbers of devices via configuration profiles but it has a number of requirements such as Google Play services and an active internet connection.
Do not use XML files if you are using remote management (they are not imported automatically from v2.0.36 onwards).
Please note that you may find this feature no longer works in Android 9.0 and later due to SDK security changes, if you find this feature no longer works then we would recommend switching to an automatic configuration JSON hosted on your own webserver, which you can find information on here: Automatic Configuration JSON
You can create an XML file from scratch but it's far easier to configure 1 device with the settings you need and Export the XML file via Settings > Admin > Export to XML. This will create a file called kioskbrowserconfig.xml in the root of the device' default storage.
Kiosk Browser will automatically Import settings from kioskbrowserconfig.xml when stored in the root of the device' default storage. Please note this will only happen on first launch and not once Kiosk Browser is loaded into memory. So for testing purposes you can either reboot the device or force stop Kiosk Browser via Settings > Apps.
If kioskbrowserconfig.xml remains stored in the same location, each time Kiosk Browser is first launched it will be re-imported.
Deleting XML File on Import
If you only want the configuration file to be imported once, you can specify a delete command within the XML file so that kioskbrowserconfig.xml is automatically deleted once a successful import has occurred. Just modify the existing preference key in the XML file as per below:
Updated on: 17/01/2023
Thank you!