Launch App After Installation Option Not Persisting in App Policy Settings
Summary
Related SOTI ONE Platform Products
Related Device OS
Issue Description
In SOTI MobiControl 2024.1.0, after toggling the "Launch App After Installation" option in the App Policy, the setting does not persist
Using Developer Tools, the configuration incorrectly saves as 'false' instead of 'true' when enabled.
Environment
This issue is observable in the App Policy configuration for Android devices and when monitored using the Developer Tools network logs in Chrome or Edge browsers.
Symptoms
- The toggle for "Launch App After Installation" is changed to enabled, but reverts back to 'false' upon saving.
- No error logs are generated in UI and MS logs for the failed configuration.
- Developer Tools show enterprise log indicating 'LaunchOnInstall' is false.
Prevention
Validate toggling settings after saving in the App Policy, and always test the functionality after policy updates.
Cause
The root cause appears to be a misconfiguration in how the application policies save the installation settings, leading to the incorrect value being recorded for the 'LaunchOnInstall' parameter.
To validate this issue:
1. Navigate to the affected App Policy in your SOTI console.
2. Open the App Policy and select Edit.
3. Select the specific app, then click the three vertical dots next to it and choose Configure.
4. In the Installation Options, toggle the Launch App After Installation option.
5. Open Developer Tools in Chrome or Edge, go to the Network tab, and start recording logs.
6. Save the App Policy configuration.
7. Observe the network logs, looking for the googlePlayStore entry.
8. Select the googlePlayStore log and view the Payload tab.
9. Verify that the LaunchOnInstall value matches the configuration (it should be 'true' if enabled).
Issue Resolution
Upgrade to SOTI MobiControl 2024.1.1 or later.
Workarounds
There are no workarounds.
Was this helpful?
Thanks for your feedback