Troubleshooting AirWatch App Wrapping

If you have problems wrapping an application or if a wrapped app fails, try troubleshooting steps to find and fix the issue.

General Troubleshooting Steps

Try the following steps.

  • Remove Workspace ONE UEM from the process.
  • Check the communication with VMware Workspace ONE Tunnel.
  • Review app wrapping logs

Send Logs for iOS (Swift) Apps

iOS (Swift) app users can select Send Logs from the wrapped app. This setting can send logs after a fatal error occurs in the initialization of the Workspace ONE SDK. To use this feature, ensure to configure two settings in the assignment in the Workspace ONE UEM console.

  • Add the key-value pair EnableSendLogsOnFatalError as a Boolean set to True.
  • Enable Managed Access.

Troubleshooting No Static Method Error

If a wrapped Android application fails on the device, check ADB device logs for a No Static Method error message.

java.lang.NoSuchMethodError: No static method 
addAccessibilityStateChangeListener  in class 

This error displays when a developer built the original application with a dependency or library not supported by the app wrapping system.

The app wrapping system can wrap applications built with non-supported dependencies and libraries but those applications fail on devices.

Requesting App Wrapping Logs

Request logs for your wrapped applications in the console and the system writes an application log. Another type of log for wrapped apps is the crash log. The system automatically writes this data when the wrapped application crashes.

  1. Navigate to Devices > List View and select the device.
  2. Select the Apps tab and choose Request Logs. The Request Logs button displays after you select the application.
  3. Navigate to Apps & Books > Applications > Logging > App Logs.
  4. Find the log for the application with the App Name column and download the file.

App Tunnel and Per-App VPN as a Wrapping Alternative

An alternative solution to app wrapping is to use the App Tunnel and Per-App VPN. This alternative does not require the maintenance associated with re-wrapping applications after a wrapping engine update. It works as an alternative if you only want the application to tunnel into the internal network to access resources. If you do not need advanced management features for the application, then consider using tunneling and per-app VPN.

Per App Tunnel and VMware Tunnel Component Explanations and Configurations

The Per App Tunnel component and VMware Tunnel apps for iOS, Android, Windows Desktop, and macOS allow both internal and public applications to access corporate resources that reside in your secure internal network. They allow this functionality using per app tunneling capabilities. Per app tunneling lets certain applications access internal resources on an app-by-app basis. This restriction means that you can enable some apps to access internal resources while you leave others unable to communicate with your back-end systems.

This alternative solution is different from app tunneling with app wrapping because it supports both TCP and HTTP(S) traffic. It works for both public and internally developed apps. However, for internal apps, the VMware Tunnel app acts as an alternative option only if the sole requirement is tunneling into the internal network. Otherwise, you must use app wrapping to take advantage of features including integrated authentication, geofencing, offline access control, and so on.

After configuring and installing VMware Tunnel with the Per-App Tunnel component, the workflow to enable and use per app tunneling in Workspace ONE UEM includes:

  1. Creating a VPN profile for your end-user devices. These profiles depend on your device platform.

    If your platform uses user profiles and device profiles, such as Windows Desktop and Android, you must create user profiles.

  2. After creating a VPN profile, push the profiles and the apps to the devices.

    For iOS and Android platforms, you must enable the Use VPN check box on the Deployment tab of the Add Application page to use app tunneling.

Windows Desktop devices use the native Per-App VPN functionality. Add the apps to the VPN profile to enable Per-App Tunnel functionality.

Note: VMware Tunnel does not support Per-App VPN functionality for macOS devices. You can restrict access to domains through the Safari Domains feature of the Network Traffic rules.

Additional Details for Per App Tunnel and VMware Tunnel

An on-demand feature lets you configure apps to connect automatically using VMware Tunnel when launched. The connection remains active until a time-out period of receiving no traffic, then it is disconnected. When using VMware Tunnel, no IP address is assigned to the device, so you do not need to configure the network or assign a subnet to connected devices.

In addition, iOS apps can use the iOS DNS Service to send DNS queries through the VMware Tunnel server to the DNS server on a corporate network. This service allows applications such as Web browsers to use your corporate DNS server to look up the IP address of your internal Web servers.

check-circle-line exclamation-circle-line close-line
Scroll to top icon