Firstly I noticed that after sending the script unlock, the logs need to update to state “Custom log (New authentication password applied)” before sending the kill_application and/or start script.

After I did this I noticed that my test device successfully completed the scripts correctly each time – however, I then started sending them to other devices and was finding they hadn’t worked. This then has led me to find another issue:

I believe what is happening is – if the device is pressed or touched by the user once the script is sent – then the following scripts:

kill_application com.commontime.infinity.jobmenuprod

start com.commontime.infinity.jobmenuprod

will work correctly. However, if the user does not touch the device at all once the script is sent (I have found 30-60 seconds or more) then the final script is not correctly ran. The device appears to run the start script once the user opens or touches the device, but if this does not happen then the script is not ran at all – almost as though the device forgets that that start script needs to be ran.

I have also tried sending it at three separate scripts – firstly sending the script unlock, and waiting for the logs to update to state “Custom log (New authentication password applied)”, next sending the kill_application script and waiting for this to appear in the logs, and then finally sending the third script – start. Again, if I press or enter the device manually as soon as the final script is sent, then the application does load once the screen is opened – yet, if I wait and enter or select the device after 30-60 seconds or more the application does not start – again as though the device has forgotten it needs to complete the third and final script.

To confirm in all instance – the unlock and kill_application scripts are correctly working each time – it is just the start application that is causing an issue.

Please could you provide any advice on how I can ensure the scripts each run - without user interference?

Thank you