• Large-scale deployment (no limit on the number of clients).
• Distributed applications not checked by Apple.

• requires an HTTPS server to distribute the application.
• requires a more expensive Apple Developer Account membership.

Step 1: Distribution certificate

• the private key is kept by the developer and is used to sign application installation packages.
• the public key is distributed with the application and must be signed by Apple.

1. Creation of the private and public key on the Mac.
2. Sending the public key to be signed by Apple, as a Certificate Signing Request (CSR).

1. Click "Certificates, Identifiers & Profiles" in the sidebar.
2. Then click "+" to create a new certificate (in the "Software" section, choose "In-House and Ad Hoc").
3. Once the CSR is generated, it must be sent to Apple.
4. Click "Choose file" and select the CSR file generated by the assistant.

• downloaded via the "Download" button,
• installed on the Mac (double-click the downloaded file).

Step 2: Application identifier

1. In the "Certificates, Identifiers & Profiles" section, select the second entry in the left-hand menu: "Identifiers",
2. Click "+" to create a new App ID,
3. In "Register a New Identifier", select "App ID" and click "Continue".
4. Describe the application to create the App ID.
   • Platform: select iOS, tvOS, watchOS for a WINDEV Mobile application.
   • Description: this field is free and allows you to enter a description of the application.
   • Bundle ID: select "Explicit" and enter a bundle identifier. There are no rules for entering this identifier. It must be specified in the WINDEV Mobile generation wizard (see step 5). By convention, this identifier often corresponds to a syntax called "reverse domain name".
     For example, for a "WMShopping" application distributed by the company "precilia.com", the recommended Bundle ID is: "com.precilia.wmshopping"..
     Note: "Bundle IDs" of the "Wildcard" type (i.e. with a star instead of an application name like "com.precilia.*") allow you to have a single App ID for several applications, which can be useful for distributing a large number of applications. However, Push notifications or In-App purchases cannot be used in an application identified by a Wildcard Bundle ID.
5. In "Capabilities", specify the functionalities used by the application (e.g., push notifications).
6. Click "Continue".
7. On the next page, specify how the application will be deployed (so that the generated App ID is compatible with In-House deployment).
8. Select "Yes. I have details on this app and plans for distribution".
9. Indicate the approximate number of client devices.
10. Then select the application deployment method:
    • via a secure website (our case),
    • via an MDM solution (Mobile Device Management, i.e. an infrastructure for managing a fleet of mobile devices).
      WINDEV Mobile allows you to implement this type of solution. For more details, see Deploying via a Private Store.
11. Next, specify how the access to the application will be secured:
    • via a login/password mechanism,
    • by forcing the user to connect to an Intranet or a specific VPN.
12. Finally, indicate the intended users of the application:
    • employees of the company,
    • contractors.
13. Don't forget to check the box confirming that all the information provided is correct (at the bottom of the page).
14. Click "Continue" to create the App ID.

Step 3: Supply profile

1. In "Certificates, Identifiers & Profiles", click "Profiles" and "+" to create a new profile,
2. Select "In-House" in "Distribution" and click "Continue",
3. In the drop-down list, select the App ID created for the application and click "Continue".
4. Choose the signing certificate to use. At compilation time, the application must be signed with the private key of this certificate (see step 5). Click "Continue".
   Note: The public key must be accepted by the application's user before they can launch the application on their iPhone/iPad (see step 7).
5. Enter a name for the provisioning profile and click "Generate".
6. Click "Download" to download the profile and double-click on it to install it in Xcode

Step 4: Web server configuration

1. Select the server and click "MIME Types" in the right view ("IIS" section).
2. If the ".ipa" and ".plist" extensions are not declared on your server, add them by clicking "Add..." (in the menu on the right of the window):
   • the ".ipa" extension is associated with the MIME type "application/octet-stream",
   • the ".plist" extension is associated with the MIME type "application/x-plist".

Step 5: Application generation

• In the first step of the wizard, enter the Bundle ID of the application.
  

• In the "Signature" step, specify the different signature settings.
  • If the Apple account used to deploy is configured on the compiling MAC: In this case, the Apple account manager gives all rights to the developer when compiling on the MAC.. WINDEV Mobile can automatically generate the necessary elements to sign the application. To do so, simply enter your team identifier (App ID Prefix or Team ID). This identifier is displayed in the upper-right corner on all pages of the Apple Developer site when you are logged in.
    Alternatively, you can use the "Import" button to select the ".mobileprovision" file: the associated Team ID will be automatically imported and filled in..
  • If the Apple account is not configured on the compiling MAC: In this case, the Apple account manager doesn't want to give full rights to the developer. WINDEV Mobile allow developers to "Manage the signature manually". In this case, you need to import the "Distribution profile" (".mobileprovision" file) and the "Development profile" (you can use the same ".mobileprovision" file, or a different file, depending on your case).
  • Alternatively, you can fill in the signature details directly in XCode, on the Mac used for compilation.
  For more details on iOS app signing, see Signature of iOS applications.
• Finish the wizard to generate the Xcode project and copy the result to your compilation Mac.

Step 6: Compiling in Xcode

1. Load the project in Xcode.
2. Select the "Generic iOS Device" target in the toolbar.
3. In the "Product" menu, select "Archive".
4. When the creation of the software archive is complete, click "Distribute App".
5. For In-House deployment, select the "Enterprise" distribution method and validate by clicking "Next".
   Tip: In the distribution options, you can reduce the package size if all client devices are of the same model.. To do this, choose the model from the "App Thinning" drop-down list.
   Warning: do not select "All compatible device variants".. For an application compatible with all device variants, select "None" (default option)
6. Be sure to check "Include manifest for over-the-air installation".
7. Click "Next".
8. Specify the details in the deployment manifest before validating ("Next"):
   • Name: specify application name
   • App URL: specify the address at which you wish to make the installation package available.. This package is an .ipa extension file, and an HTTPS access is mandatory.
   • Display Image URL: enter the address of a 57x57 pixel image to be used as the installation icon for the application.. The protocol must be HTTPS.
   • Full Size Image URL: enter the address of a 512x512 pixel image to be used as a large icon for the application.. The protocol must be HTTPS.
9. For In-House distribution, the installation package must be signed again after the generation.
   In this step, you can let Xcode manage the signature automatically (based on the information specified in the provisioning profile).
   If you manage singing manually, an additional step requires you to confirm the signing certificate to use (crated in step 1) and the provisioning profile (created in step 3).
10. After validating ("Next"), Xcode builds the installation archive of the application, then signs this archive with the private key of the signing certificate.
    Note: this operation can take several minutes.
11. Once the distribution archive has been created, Xcode proposes to export the result of the generation. Xcode then generates several files in this directory. Two of them are necessary to distribute the application:
    • manifest.plist,
    • the .ipa file (name chosen in the archive creation wizard).
    Warning: if there are several .ipa files in the export, this means that one of the previous options has not been correctly selected: you need to restart archive generation, and in particular check that the "None" option is selected in the "App Thinning" combo.
12. Copy these two files to the Web server (configured in step 4) at the URL specified during generation.

Step 7: Installing the application

1. Open the page on Safari and click the installation link.
2. Safari will then display a confirmation box indicating that the website wishes to install an application: click on "Install".

1. Go to "Settings", "General",
2. Tap "Profiles & Device Management",
3. Tap the name of the signing certificate in "Enterprise App" (this is the certificate that was created in the first step),
4. Tap "Trust ..." and validate.

Step 8: Pilot Xcode (optional)

• Clean compilation cache:
  
  xcodebuild clean
• Archiving:
  xcodebuild -scheme <my_scheme>-sdk iphoneos-archivePath <archive_path> archive
  
  The parameters are as follows:
  • <mon_scheme>: value of a project scheme (see your application's schemes in Xcode).
  • <chemin_archive>: destination path.
• IPA build:
  
  xcodebuild -exportArchive-archivePath <my_scheme>.xarchive
  -exportOptionsPlist exportOptions.plist-exportPath <export_path>
  
  The parameters are as follows:
  • <mon_scheme>: value of a project scheme.
  • <chemin_export>: destination path.