Avalanche 6.0 - 6.1 - Creating and Deploying App Payload to Android & iOS Devices / Issues with payloads and packages

Version 9

    Verified Product Versions

    Avalanche 6.1Avalanche 6.0


    Avalanche 6.1 base installation with Android smart-devices enrolled



    Move to the Profiles tab and then select the folder you wish to install the profile to. As with previous versions of Avalanche, profiles stored in a parent directory will be applied to lower directories.


    Click on the + icon to create a new Payload. Payloads are the contents of a Profile and can be an APK, AVA, cfg, etc.



    Select the device platform and the payload type. IOS payloads only go to IOS devices, Android Payloads only go to Android Devices. Each platform will have different options. To install an APK on a device select the Software radio button.



    Next type in a Payload Name; this is the name that will display in Avalanche. Then select Deployment method. This section identifies whether you want to have the app install automatically or if it is an optional download from corporate app list. We now need to choose the Software Hosting options. If the device has access to the Play Store and the app is hosted on the Play Store use the “Google play store” option if not you will need to use the Manifest URL. The Manifest URL is used when you are going to host the app on your own. When using the manifest URL you will need to provide the Package ID, Manfirest URL, and the Package Version.


    Android packages require you to use a Package ID which is identified within the APK file. to do this you will need to change the file extension to .zip. Next locate the AndroidManifest.xml file and you will be able to find the Package ID there. An example of a Package ID would be com.wavelink.android. The Manifest URL is the url where the package can be downloaded. Finally the version ID is the version of the package you are looking to install. if there is a mismatch with version ID there will be an issue.  (This can be found in the manifest.xml file, which is located within the APK and can be accessed after converting the APK to a zip file) The APK will not install properly if the Package ID and Package Versions are incorrect.



    NOTE: If the package is continuously re-installing verify that the Package Version matches the AndroidManifest.xml within the APK file. They most likely do not match exactly. The Package Version should be retrieve from VersionName property instead of VersionCode.


    Next we will add the Payload to a Profile. You can either create a profile or apply the package to an existing profile. In this scenario we will create a profile.


    Note: You have to reference the plist in the software payload not the ipa.



    Click on the + within the Available Profile section.



    Select the type of Profile you will be installing the app to



    Now you will see the profile show up within the Available Profile section. If you are finished with adding payloads to the profile select the check box next to your profile and click the apply button



    You will then be asked to create your selection criteria and then asked to schedule a criteria



    The profile is now within the Applied Profiles section and notated with the Needs Deployment flag. Schedule a deployment on the server and your enrolled devices will begin pulling the new profile.