SOTI Pulse Logo

chrome issue

GP
Gareth Perry

Hi,

We have added a button to our lockdown that opens a web link in chrome. the command for the button is 

 
this works as expected and opens the correct URL. the user has to log in to the webpage which they can do fine. The issue is that the website isnt very good and the logout doesn't log them out fully.
 
If you go back to the lockdown screen and then click the button again then you browse to the link but the website still thinks you are logged in so bypasses the login screen and then falls over because the session has timed out.
 
the only way i can clear is to delete the browser cache and data. This isnt ideal for the end user.
The end user cannot close the browser either.
 
also when they go back into chrome it opens another tab so you end up with lots of tabs.
 
we have added another button to the lockdown called logout that runs a script on the device with 
kill_application com.android.chrome
wipeapplication com.android.chrome
 
the kill works but then has an effect on the device where when you press on the screen, the device thinks you have pressed elsewhere on the screen
 
the wipe does not seen to do anything
 
We are using honeywell EDA51 with work profiles in mobicontrol.
 
any help much appreciated
 
thanks
 
gareth
4 years ago
Android
ANSWERS
J
JSMOD@SOTI
4 years ago

Hi Gareth,

Thank you for posting on SOTI Central.

Have you tried using SOTI Surf browser to achieve what you are looking for? What you have described above seems to be a limitation of the website, but this way you will have greater control over the browser with a Profile configuration. You can also clear the cache for Surf when necessary via the below script or from the Web Console > Device Actions > 'Clear SOTI Surf Cache'.

sendinfo net.soti.action.surf clearcache

Also just so you know, the 'wipeapplication' script is not supported on Work Profile devices. If Surf is not suitable for your needs then I would suggest enrolling as Enterprise Work Managed, install the device Plugin and try the script again.

Kind regards,

GP
Gareth Perry
4 years ago

Hi,

thank you for your response. I believe we are already on Enterprise work managed and have the relevant plugin installed.

The issue with the screen not detecting the area that is being pressed correctly, only appears when we remote onto the device. using the device directly works as expected.

We will continue with our current solution

thanks

Gareth

Similar Discussions