View the supported platforms, bit versions, architectures, console versions, and environments for wrapping apps. Use supported systems to ensure that the solution integrates with your mobile deployment.

The application that you wrap must be compatible with the following components. If an application was built with an Workspace ONE SDK older than the version listed, it is not compatible with app wrapping.

Table 1. Supported Platforms and Bit Versions
Platform Bit Versions and Architectures Supported Workspace ONE UEM Console Version
Android v5.0 or later



With the support of 64-bit architectures, expect a size increase of your wrapped Android apps when compared to previous app wrapping releases.

Workspace ONE UEM console v1902 or later
iOS v11.0 or later


Workspace ONE UEM console v1902 or later

Supported Android Components

  • Build the app with the Android API level 21 or later. Older versions of the Android API do not build applications that are compatible with app wrapping.
  • Use the Android GMS library v16.0.0 for Google Play Services because it is the only supported version.
  • Use SQLCipher for Android 4.2 or later.

Supported Deployments and Requirements

App wrapping is available for the following deployments, using the SaaS-Hosted app wrapping engine to wrap internal applications. The feature does not wrap public or purchased applications.

Table 2. Supported App Wrapping Engine and App Type by Deployment Type
Deployment App Wrapping Engine App Type
SaaS Workspace ONE UEM SaaS-Hosted App Wrapping Engine Internal Applications
On-premises Workspace ONE UEM SaaS-Hosted App Wrapping Engine Internal Applications

Store Apps Do Not Wrap

You cannot wrap applications from app stores, even if the APK or IPA comes from the vendor directly. Contact vendors to see if they can incorporate the Workspace ONE SDK and AppConfig into their applications to address enterprise requirements.

Android Apps Built with Crosswalk Project Libraries Do Not Wrap

Crosswalk on Android provides a packaging tool and a Java wrapper layer. They can bundle Web applications into the Android Web app APKs. This Java wrapper layer calls Crosswalk runtime, and Crosswalk runtime is a full-featured Web engine mostly written in C/C++. Android platforms do not package C/C++ code into SMALI files, and the app wrapping solution cannot modify and wrap the C/C++ libraries and code.

iOS App Wrapping Requirements

  • If @executable_path/Frameworks is missing from the Xcode build settings in LD_RUNPATH_SEARCH_PATHS of the build target, add it to Xcode build settings. If you do not add this and you are using the most current wrapping engine, the app crashes after wrapping.
  • If your iOS app is Swift based, use Swift 5.0 or later.
  • iOS Developer Enterprise Account - Use this account to get Xcode used to compile the application as part of the wrapping process. Go to for information. Use this account type to develop iOS applications for use internally and not to deploy to an app store.

    To develop internal applications, ensure to get auxiliary files for enterprise (internal) distribution and not app store deployment.

  • Mobile Provisioning Profile - Get this file from Apple's Developer Portal. Get this profile for enterprise use, because it is specific to your application and to the Code Signing Certificate. The bundle ID of the provisioning profile matches the bundle ID of the IPA file.
  • Code Signing Certificate - Get this file from Apple's Developer Portal. Get this file for enterprise use and not app store distribution, and use it to sign the wrapped application.
  • Sign the iOS Binary - Sign the application with the provisioning profile and the signing certificate before wrapping the application.