This article explains how to finish the wrapping process, by actually wrapping your application with the App47 agent, re-signing your application with a new certificate and upload to the App47 server.
You must have an Enterprise Account with App47 to use this feature. This step connects to the server and verifies the account status.
Once connected, the Account window will contain the following areas:
IPA File and Upload to server
How to Wrap your App
1. Select an app in the app list
On the left side of the window, you will see a list of private apps already created in the account.
Select the app you wish to upload a new build.
2. Build Information
The build information are allows you to add release notes, set the version number for the newly signed app and set if this build should be activated immediately once uploaded to the server.
3. Provisioning Profile
The provisioning profile area has three required fields.
Provisioning Profile - The mobile provisioning file downloaded from iTunes connect. Either a Ad-Hoc or Enterprise (inhouse) distribution profile is required.
Bundle ID - This must match the mobile provisioning profile bundle ID. It should be updated once the Provisioning Profile file is selected.
Reset bundle identifier - If you have previously uploaded a build for this app with a different bundle identifier, select this option to reset it on the server. This will prevent the build verification from generating an error.
Identity - The identity (name) associated with the mobile provisioning file. This is the certificate that was use to create the mobile provisioning profile. The certificate must be in either your default keychain, or the Keychain file identified in the next field.
Keychain - Name of the keychain file to use, if none is given then we'll use the system default keychain.
Entitlements - Specify an entitlements file to use during signing, please see https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/codesign.1.html for more information.
Resources - Specify a resources file to use during signing, please see https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/codesign.1.html for more information.
Requirements - Specify a requirements file to use during signing, please see https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/codesign.1.html for more information.
4. Agent Configuration
The agent configuration area allows you to set the configuration parameters for the App47 agent that is added to your application as part of this process.
|Inject embedded agent…||Turn on/off the injection of the embedded agent into your application. By turning this off, you will not receive analytics, crash logs and other App47 services.||Yes or no|
|Delay data upload||The amount of time in seconds the agent will wait after the application starts up to send data to the server. This allows your application time to update the UI before the agent begins to work.||Any integer greater than 0|
|Update frequency||How often the agent will check in with the server to update its configuration.||Monthly, Bi-Weekly, Weekly, Daily, Twice a Day, Hourly, and Every launch|
|Send events immediately||If the agent should send timed and generic events immediately, or batch them up and send at the next start of the application||Yes or no|
|Capture location||If you want the agent to collect location information, the app must already have CoreLocation already compiled into it for this option to work correctly.||Yes or no|
|Upload on exit||If the agent should attempt to upload data on exit.||Yes or no|
|Capture crashes||If the agent should register an exception handler to capture unhanded exceptions (crashes). If you are wrapping an app that already has an analytics library, do not select this as it may conflict with the original library.||Yes or no|
5. IPA File and upload
Once the information above is properly completed, simply drag your IPA to the drop area and click the Upload to server button. This will start the process to inject the agent library, resign the application with your distribution profile and finally upload the newly signed app to the server.
If you have Activate Immediately set to Yes, and the build is valid, all users that have access to this app will be notified of the new version.
The reasons the build may be invalid include:
The version number specified in the build information area already exists on the server.
The provisioning profile is a development profile, not an ad-hoc or enterprise distribution profile.
The bundle id specified in the code signing area is different than builds already uploaded for this application.
Click the View builds on server to see the newly uploaded build.