For applications which are uploaded locally for internal distribution (either during production or testing), the following steps are taken to establish trust:

1. Sign the APK file with Android Studio Keystore. If you use the Debug Keystore from Android Studio, you can whitelist the app for debugging from the local IDE. However, if you use Release Keystore, the app is not eligible for debugging.
2. Upload the signed APK file to AirWatch Admin Console.
3. The AirWatch Admin Console extracts the application's public signing key.
4. The AirWatch Admin Console whitelists the application's public signing key with the AirWatch Agent.
5. When the application is launched, it calls AirWatch SDK for initial configuration.
6. The AirWatch Agent validates the signing key by comparing it to the one uploaded in the AirWatch Admin Console.

The automatic key whitelisting feature is currently only supported with Internal Apps. However, the trust for the Public Apps using AirWatch SDK can be established by manually whitelisting the public signing key. If the app developer shares the signing key then AirWatch can follow steps similar to the Internal apps flow for whitelisting.

From the Task bar, click on the Android Studio icon to launch it.

NOTE - Android Studio may take several seconds to launch, please be patient while it opens.

Click Open an existing Android Studio Project.

1. From the windows, select C:\Users\holuser\Documents\HOL\Android SDK.
2. Select Android SDK 16.02.
3. Select sample code.
4. Select airwath-sdk-test-app.
   NOTE - Android Studio can auto-detect the Android Project files and will put Android Studio icon before for easier identification and access.
5. Click OK.

1. Select the View Project from the drop down if it is not already selected.
2. Expand the root airwatch-sdk-test-app.
3. Right click on the folder libs.
4. Select the option Show in Explorer.

Double-click the libs folder.

1. Validate that you have AirWatchSDK-16.02 Jar file, AWFramework 16.02.aar and gson-2.4 jar file included in the libs folder. You will see a lot of other libraries but these three are the primary libraries that are used for this lab.

NOTE - If you do not see these libraries in the libs folder, then you can add those from the SDK package. These files are located in \Documents\HOL\Android SDK\Android SDK v16.02\libs\AWFramework and ClientSDK folder. The following step demonstrates how to add the gson library to the project libs folder.

For any SDK app, the developer needs to add the related libraries to the libs folder of the project, otherwise the project might not build correctly. To limit the scope of this lab, most of the files are already added in the correct folder for you. In this section, we are going to add the gson library as an example.

For troubleshooting any build errors, we should always check if the required libraries are added or not as the first troubleshooting step.

NOTE - Perform this step ONLY if you don't see gson library in your project's libs folder. Follow similar steps for AirWatchSDK jar file and/or AWFramework aar file in case they are missing in the libs folder.

1. From the taskbar at the bottom of the Desktop, click on the icon to launch File Explorer.
2. In the new Window, navigate to Documents\HOL\Android SDK\Android SDK v16.02\libs\ClientSDK.
3. Right Click on gson-2.4 executable JAR file.
4. Click on Copy.
5. In another Window for libs folder (if you closed it, then reopen from Android Studio as described in the step above), Right Click on click on Paste to add the gson library. Close or minimize the Explorer window.

To limit the scope of this lab, all the coding has already been implemented in the project. We have also verified that the project has the required libraries and added the gson library. Now it is ready to be built.

Back to the Android Studio window,

1. Select the root airwatch-sdk-test-app.
2. From the toolbar, select Build.
3. Select the option Build > Rebuild Project. This will start the build.
4. Select the perspective Gradle Console From the bottom right.
5. Scroll to the bottom of the Gradle Console.
6. The build time may vary depending on the VM configuration but after some time (approximately 2 minutes), you should see the status as BUILD SUCCESSFUL.

1. Select the root airwatch-sdk-test-app (if not done already).
2. From the toolbar, select Build.
3. Select the option Generate Signed APK...

For this lab, keychain and keychain alias is already setup for you and is encrypted with a Master Password. When prompted,

1. Enter the password as "VMware1!".
2. Click on OK.
3. Keep all the defaults and click on Next.

NOTE - The keychain is located at C:/Users/holuser/Documents/HOL/Android SDK/awks.jks and alias is auto-populated when you make the selection.

For easier access, we are going to save the application on the Desktop.

1. Click on the Browse icon.
2. Click on the Desktop icon to select the destination folder as Desktop.
3. Click on OK to continue.

1. Select the Build Type as release.
   NOTE - If we select the build type as debug, it will allow us to run the app in the debug mode by connecting the device to the Computer and troubleshoot via Android Studio debugger. However, to limit the scope of this lab, we are going to sign the app with the release key.
2. Check the V1 (Jar Signature) checkbox.
3. Click Finish to start the process. Depending on machine resources, it will take anywhere from 2 to 3 minutes to complete the APK generation process.

While we are waiting to generated the signed APK, let us go ahead and create the SDK profile which we will assign to our sample app while uploading it to the AirWatch Console.