Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »


This page provides a checklist of prerequisite application requirements that app developers can use to ensure that the apps they are providing to EASE administrators are ready to be uploaded to EASE. For a more detailed description of what this requirements are and what they entail, see Understanding the Requirements.

Checklist for Application Developers


To send the checklist above to your application developer, you can copy and paste it into an email or document.

On This Page

Understanding the Requirements

Make sure the app is signed

It is imperative that all applications an administrator plans to upload to EASE are signed before the upload process. If an application is not signed prior to being uploaded to EASE, an error message will display and the application will not be able to be uploaded.

Obtain a list of entitlements that are enabled for the application

It is important that the administrator who is uploading and signing an organization's applications has all the relevant information for a particular app's enabled entitlements. When an administrator signs an app, they need to sign it with a distribution provisioning profile that has entitlements (app services) that match the entitlements (capabilities) built into the app. If the entitlements don't match, users will not be able to install the app on their devices. If the app includes app extensions, each extension must be signed with a different provisioning profile that has the correct entitlements.

It is best practice for the EASE administrator to obtain a list of an app's entitlements from the app's developer before he or she attempt to sign an application. This is helpful to ensure that the administrator is signing with an appropriate distribution provisioning profile(s). If this information is not made available to the administrator, EASE can help. When uploading a provisioning profile in the Sign with New Credentials section of the Signing tab, EASE compares the entitlements in the profile with the app/extension. If the entitlements don't match, EASE will warn the administrator and clearly identify what doesn't match. With this level of information, administrators can follow up with the appropriate member of their team to generate the necessary provisioning profile(s) from the Apple Dev Portal. 

For more information on entitlements, see Entitlements. For instructions on signing with new credentials, see Sign with New Credentials.

Obtain a list of the application's extensions

After Apple's release of iOS 8, it is now important that the administrator who is uploading and signing an organization's applications is made aware of whether a particular application has extensions or not. If an app contains extensions, the administrator needs a separate explicit distribution provisioning profile to sign the app and each extension in the app. If an app contains a WatchKit app for Apple Watch, the administrator also needs one distribution provisioning profile for the WatchKit app and one for the WatchKit app extension.

For more information on extensions, see App Extensions and WatchKit Apps. 

Check that the application is built with icons that are optimized for different screen resolutions

Developers should include application icon images with resolutions that are tailored to the specific form factor(s) they are targeting. EASE requires an application to have at least one app icon in PNG format with a resolution of 114 x 114 pixels, but it is a best practice to include multiple icons that are optimized for different screen resolutions. EASE will extract the highest resolution icon image found in either the info.plist (for iOS) or the App Manifest (for Android) to display in both the EASE Portal and the App Catalog. Even when an icon is extracted from the app, you can upload a different icon to EASE. The icon you upload will be displayed only in the EASE Portal and the App Catalog, but the icon bundled with the application file will still be used to display the app on the Home screen of the user's mobile device once the app is installed.

Make sure the app is not signed with an app store distribution provisioning profile

Apps signed with an App Store distribution provisioning profile will not upload correctly to the EASE Portal. Instead, apps should be signed with either an In House or Ad Hoc distribution provisioning profile. For more information on creating the correct distribution provisioning profile, see Distribution Provisioning Profiles.

Reviewers: Will the app not upload correctly? or will users just be unable to install the app? And what exactly is the issue with an app store distribution profile? Why will it not work correctly?

Make sure a standard folder structure has been used inside the IPA file

If an app is built with a non standard folder structure, it will not upload to the EASE Portal correctly. IPA files should have only one folder inside them called "Payload", and only one folder, containing their .app files, should be inside that folder.  

Reviewers: Will the app not upload correctly? or will users just be unable to install the app? What exactly is a non-standard folder structure?

  • No labels