The AirWatch App Wrapping engine adds Workspace ONE SDK functionality to wrapped apps when you deploy them with the Workspace ONE UEM console.
SaaS deployments do not configure this option because it is already configured.
The AirWatch App Wrapping engine communicates with your network server in your on-premises environment to deploy Workspace ONE SDK functionality to wrapped apps.
In the Workspace ONE UEM console, navigate to Groups & Settings > All Settings > System > Advanced > Site URLs.
Select Enable App Wrapping in the app wrapping section.
Complete the entry for your platform.
Turn on Cloud Services for increased security for app wrapping communications with the use of HMAC authentication.
Disable Cloud Services to troubleshoot app wrapping issues, but this action reduces security because it bypasses HMAC authentication.
In the Workspace ONE UEM console, navigate to Groups & Settings > All Settings > Admin > Cloud Services.
Select App Wrapping Secure Communication Enabled. If the application fails to wrap, you can disable the check box and try to wrap again. However, clearing the check box bypasses the HMAC token authentication check, making this option less secure.
Check the Auto Discovery AirWatch Id entry in the AirWatch ID section (on the same page as the Cloud Services section). This ID is your Workspace ONE UEM credentials and provides a secure connection with the Workspace ONE UEM Cloud.
Configure a profile to add Workspace ONE UEM functionality to your app with the Workspace ONE SDK framework.
In the Workspace ONE UEM console, navigate to Groups & Settings > All Settings > Apps > Settings and Policies > Profiles.
Select Add Profile and choose App Wrapping Profile and the applicable platform.
Configure General settings and then complete the settings for the desired features (payloads). You select this profile on the App Wrapping tab when you upload and deploy the app.
Select the applicable organization group and upload your app and assign the correct profile to wrap it.
In the Workspace ONE UEM console, go to Apps & Books > Native > Internal > Add Application to add your app to the console.
On the App Wrapping tab, select Enable App Wrapping.
For App Wrapping Profile, select the AirWatch App Wrapping profile you created earlier.
Select Save & Assign to move to the app assignment process.
For iOS (Swift) apps, use Send Logs from within the app. You must configure the Restrictions and Application Configuration tabs in the Assginment wizard.
In the Workspace ONE UEM console, add an assignment or edit one for the app.
On the Application Configuration tab, comple the following entries.
Deploy the assignment to devices in the selected organization group.
Applications require re-wrapping for several reasons that include app wrapping engine updates, operating system changes, and system fixes. The console identifies wrapping issues in the console so you know to re-wrap an application.
Build a new version of the app so that it has a version number that is greater than the currently deployed version in Workspace ONE UEM.
Upload the rebuilt app to Workspace ONE UEM in Apps & Books > Applications > Native > Internal.
Use the app wrapping tab to re-wrap the application.
Workspace ONE UEM does not push a wrapped app to devices until the wrapping engine reports wrapping success. Find the success status in the Workspace ONE UEM console at Apps & Books > Applications > Native > Internal and view the Wrap Status column.
If wrapping fails, use the Queue App For Wrapping check box on the App Wrapping tab, which only displays upon failure. The wrapping engine re-wraps the application after you select Save & Publish from the flexible deployment page. When the wrapping engine reports success, Workspace ONE UEM pushes the application to devices. This work flow prevents pushing failed wrapped applications to devices.