I don't believe the issue is with the Surf app itself but rather with how the new AE SOTI agents are attempting to auto-grant permissions silently. If you include a post-install script along with your APK installer package to set all of the required permissions using the scripts that you've already provided then you should be all set.
Has anyone tested SOTI surf 14.3.1 Build 2 (April 02, 2019) yet?
If so, have SOTI fixed the additional 2 permissions that have to be agreed to stop SOTI surf crashing?
I'm not talking about the permission of the agent itself, but the permissions that are under additional permissions for the soti surf app. The two of them are permissions to discuss with the mobicontrol agent, something like that.
These two are the ones needed to get surf working.
And I can confirm grant them with the script works fine.
But they are not granted by default when pushing surf, which it should, so the script is needed (but obviously shouldn't be)
You are right that app permission of the device agent itself currently cannot be managed with the afw_set_permission_grant_state script command. I have actually mentioned about this limitation earlier in another post at
Thanks for the update, I found this and used it successfully before, I forgot to update the post here.
The needed permissions are the additional ones that grant mobitonctrol agent access. The android permissions are now automatically granted, but still, the mobicontrol ones need to be set manually. My last test on that was last week, with latest 13.6 agent and latest Surf + fresh factory reset device.
Cheers for the heads up :)
SOTI support haven't mentioned that when we worked on the fault so hopefully the issue has been resolved.
When I checked, most devices are not yet on v126.96.36.1992+
What is the build numbers of your v13.6.0 device agent? If your Android Enterprise device agent is v188.8.131.522+, all required app permissions for any managed apps should have been granted automatically by default.
From my previous tests, it's found that the default may not be honored for an app if some of its permissions have previously been changed (in device's Settings or with :afw_set_permission_grant_state" command). Hence, if your Soti Surf is installed before your device agent gets upgraded to v184.108.40.2062+, there might be a need to first uninstall Soti Surf and then have it re-installed.
Hi, I had the same problem on Android Enterprise devices since allow devices to update to the current version of SOTI Surf.
After a while and working with SOTI support, I finally found a combination of SOTI script commands that set the permissions needed.
To send the script to the devices, I created a package and added that to a profile for AFW devices with a filter where SOTI Surf was installed.
afw_set_permission_grant_state net.soti.surf net.soti.mobicontrol.permission.DEVICE_INFO allow
afw_set_permission_grant_state net.soti.surf net.soti.mobicontrol.permission.DEVICE_INFO_ELM allow
afw_set_permission_grant_state net.soti.surf net.soti.mobicontrol.permission.DEVICE_INFO_AFW allow
afw_set_permission_grant_state net.soti.surf net.soti.mobicontrol.permission.GET_DATA allow
afw_set_permission_grant_state net.soti.surf net.soti.mobicontrol.permission.GET_DATA_ELM allow
afw_set_permission_grant_state net.soti.surf net.soti.mobicontrol.permission.GET_DATA_AFW allow
I did try other commands for the standard permissions as I thought might be useful to help against customers answering incorrectly when 1st opening SOTIsurf.
afw_set_permission_grant_state net.soti.surf android.permission.CAMERA allow
afw_set_permission_grant_state net.soti.surf android.permission.RECORD_AUDIO allow
afw_set_permission_grant_state net.soti.surf android.permission.WRITE_EXTERNAL_STORAGE allow
afw_set_permission_grant_state net.soti.surf android.permission.READ_EXTERNAL_STORAGE allow
afw_set_permission_grant_state net.soti.surf android.permission.CALL_PHONE allow
afw_set_permission_grant_state net.soti.surf android.permission.ACCESS_COURSE_LOCATION allow
afw_set_permission_grant_state net.soti.surf android.permission.ACCESS_FINE_LOCATION allow
Just change the 'allow' to 'default' or 'deny' if you need different options.
I am still testing everything but looking good so far.
I don't have an answer for this problem, but I have this same problem with the latest version.