Testing Applications that use the AirWatch SDK

When integrating the AirWatch SDK into your Android or iOS SDK application, it is important to test your applications for the correct integration with the AirWatch SDK, including delivery of profiles from the AirWatch Admin Console. 

To simplify the workflow of doing so, you can sideload your SDK apps directly to your devices from the relevant IDE (Android Studio or Xcode) by first uploading an initial version and pushing it down on the test device. 

Take the following steps for testing AirWatch SDK apps:

  • Enroll your test device - Your device must be enrolled in the AirWatch Console so the latter can communicate with your application.
  • Create the application record in the AirWatch Admin Console - Add your internal application to the console by uploading it and giving it an assignment. Please see the Mobile Application Management guide in the resources portal for more details. Note: You must enable the option Application Uses AirWatch SDK in the application record or the SDK does not initialize correctly. Make sure to include the appropriate SDK and Application Profiles, if applicable. 
  • Push the application to test devices - Selecting Save & Publish pushes the application to test devices using the AirWatch App Catalog. Use devices for testing that are AirWatch managed devices. 
  • Run your application in Xcode or Android Studio - Run your application in the relevant IDE. The AirWatch Admin console pushes the initialization data to the application when the application installs on test devices. You can now run the application as many times as you need to debug it

 

Appendix: Creating a debug APK build from within Android Studio:

  1. Click on the Gradle menu to the right of the IDE window:
    one.png
  2. Open the build menu under the app folder:
    two.png
  3. The APK is then generated in the outputs folder under the app folder in your project's directory. Please use the app-debug.apk
    three.png
Have more questions? Submit a request

0 Comments

Article is closed for comments.