If you have problems wrapping an application or if a wrapped app fails, try troubleshooting steps to find and fix the issue. Also, if you use Professional Services, gather specific information to help them find the issue.

General Troubleshooting Steps

General troubleshooting actions to try include to remove Workspace ONE UEM from the process, to check the communication with VMware Workspace ONE Tunnel, and to 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.

Gather Information for Professional Services

With the complexity of mobile networks, it might be necessary to involve Professional Services, if this level of support is part of the services agreed upon by the organization and Workspace ONE UEM. Pass on to them any data gathered from performing the listed troubleshooting steps.

  • Side-load the application, unwrapped, and watch the behavior. This step takes Workspace ONE UEM out of the process and ensures that the application works as expected.
  • View app wrapping logs to look for issues. See the Request App Wrapping Logs topic for details on how to access these logs.
  • If the Workspace ONE UEM console reports that wrapping failed, Professional Services can access and review app wrapping engine logs to find issues.
  • For iOS platforms, resign applications to see if the provisioning profile and signing certificate work. Side-load the resigned application and see if it works as expected.
  • For environments that use the VMware Tunnel, test the Tunnel. Access a secure site with the VMware Browser through the Tunnel to make sure that the Tunnel directs traffic as expected.
  • If the application developer used Mobile App Development Platforms, or MADPs, to build the applications, ensure that the wrapping engine supports it. See the Mobile App Development Platform, MADP Support topic.
  • Ensure that the application developer used supported methods and libraries to build the application. See the Developer Resources topic.

Troubleshoot 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. Refer to the Developer Resources for a list of supported dependencies and versions for Android.

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