Igloo Mobile Branded Edition: Distribution

Wiki HomeTitle Index

Overview

The effective and efficient distribution of the Igloo Mobile Branded Edition application is key to the success of the project and acceptance by users.

This article provides an overview of the preparation required and the information needed to distribute the application successfully.

Go to one of the following sections in this article: 

If you have any questions about the required information or the steps to obtain them, don't hesitate to contact your Igloo Project Manager for assistance.

Mobile device management

Your branded mobile application will utilize an in-house Mobile Device Management (MDM) for distribution.  MDM is an internal security software used by an organization to monitor, manage and secure employees' mobile devices deployed across multiple mobile service providers and across multiple mobile operating systems.

We assume the following:

  • You currently have an MDM operational in your organization and have experience monitoring, managing, and securing employees' mobile devices with the iOS and Android operating systems.
  • You will need to support both iOS and Android devices. These devices may be company-owned and managed, or you support a Bring Your Own Device (BYOD) policy.

Your IT Department typically manages the MDM. 

What we need from you

Igloo requires third-party vendor support to allow the application to run on a smartphone. The requirements include:

  • Provisioning information to use in the build process from Apple and Google
  • Setting up of accounts for internal testing and validation 

The following iOS and Android sections outline what information Igloo requires to deploy the application and how to obtain that information.

iOS distribution

Getting ready

To set up iOS distribution, you require:

The account will enable the use of the Apple infrastructure to provision the iOS version of the application. Please note:

  • There is an application process for the Apple Enterprise Developer Account that Apple manages
  • There is an eligibility criteria for organizations accepted
  • There may be a small annual charge to maintain 
  • Require legal authority to bind your company to the agreement with Apple

Obtaining an Apple Enterprise Developer Account is subject to review and scrutiny by Apple with no guarantee on turnaround time or acceptance.  

As part of setting up the application, you must provide the Igloo Team with the following:

  • Distribution Certificate 
  • APNs Certificate
  • Provisioning Profiles

The Igloo Team uses this information for the iOS .ipa builds. 

The iOS Distribution Certificate and the APNs certificate expire after one year. You will need to renew these before their expiry date and share this updated information with the Igloo team.

Creating a Distribution Certificate

By following the steps below, you should be able to provide the Igloo Team with:

  • Distribution Certificate in .p12 format with a password  
  • Private Key and Password

Steps to create an iOS Distribution Certificate:

  1. Log in to the Apple Developer site.
  2. Select Certificates, IDs & Profiles.
  3. Select Certificates.
  4. Select + to create a new certificate.
  5. In the Software section, select iOS Distribution and then select Continue.
  6. Upload a Certificate Signing Request (CSR) and then select Continue. If you don't have one, you can create one using Keychain Access on your Mac.
  7. Select Download to download the certificate as a .cer file.
  8. Double-click the certificate that you downloaded to add it to Keychain Access.
  9. Open Keychain Access
  10. Right-click the certificate and select Export.
    1. Select the .p12 file type.
    2. (Optional) Enter a password.
  11. Select the arrow next to the certificate to expand its details.
  12. Right-click the Private Key and select Export.
    1. Select the .p12 file type.
    2. (Optional) Enter a password.
  13. Share the required information with the Igloo Team. An Igloo Project Manager will provide details on how to share this information.

Creating an Apple Push Notification service (APNs) Certificate

By following the steps below, you should be able to provide the Igloo Team with:

  • APNs certificate in .p12 format with a password

The Igloo team uses this information to set up push notifications. 

Steps to create an APNs Certificate:

  1. Log in to the Apple Developer site.
  2. Select Certificates, IDs & Profiles.
  3. Select Identifiers.
  4. Select + to create a new App ID.
    1. Enter a description and Bundle ID, e.g., com.igloosoftware.branded.mobile.{organization_name}.
    2. In the Capabilities section, select Push Notifications.
    3. Follow the steps on the page to finish creating a new APP ID.
  5. Go back to the Certificates, IDs & Profiles page.
  6. Select Certificates.
  7. Select + to create a new APNs certificate.
    1. In the Services section, select "Apple Push Notification service SSL (Sandbox & Production)."
    2. From the drop-down, select the App ID that you created.
    3. Upload a Certificate Signing Request (CSR). If you don't have one, you can create one using Keychain Access on your Mac.
    4. Finish creating the APNs certificate.
  8. Download the APNs certificate that you created.
  9. Double-click the APNs certificate that you downloaded to add it to Keychain Access.
  10. In Keychain Access, right-click the APNS certificate and select Export.
    1. Select the .p12 file type.
    2. Enter a password.
  11. Share the required information with the Igloo Team. An Igloo Project Manager will provide details on how to share this information.

Creating Provisioning Profiles

By following the steps below, you should be able to provide the Igloo Team with:

  • The following Provisioning Profiles for MDM Distribution:
    • {your_app_name} - In-House
    • {your_app_name} - Ad Hoc
    • {your_app_name} Share - In-House
    • {your_app_name} Share - Ad Hoc

The Provisioning Profiles will use the iOS Distribution Certificate and App ID as described in the previous section. You must then create additional Provisioning Profiles of the same types on a separate App ID. 

The Igloo Team uses this information for signing and distributing iOS .ipa builds. 

Steps to create iOS Provisioning Profiles for MDM distribution:

  1. Log in to the Apple Developer site.
  2. Select Certificates, IDs & Profiles.
  3. Select Profiles.
  4. Select +to create a new In-House Provisioning Profile.
    1. In the Distribution section, select In-House and then select Continue.
    2. Select your App ID from the drop-down and then select Continue. Use the App ID that you created in the Creating an APNs Certificate section above.
    3. Select your iOS Distribution Certificate and then select Continue. Use the certificate that you created in the Creating a Distribution Certificate section above. 
    4. Enter a name for the Provisioning Profile (e.g., {your_app_name} - In-House) and then select Generate.
    5. Select  Download.
  5. Go back to the Certificates, Identifiers & Profiles page.
  6. Select + to create a new Ad Hoc Provisioning Profile.
    1. In the Distribution section, select Ad Hoc and then select Continue.
    2. Select your App ID from the drop-down and then select Continue. Use the App ID that you created in the Creating an APNs Certificate section above.
    3. Select your iOS Distribution Certificate and then select Continue. Use the certificate that you created in the Creating a Distribution Certificate section above. 
    4. Select the following Igloo testing devices UDIDs and then select Continue.
      • c6ba315377a9b4682bb839dda78458497d08942e
      • 8f948c292cb2932a752755d12bd936e56804baf6
    5. Enter a name for the Provisioning Profile (e.g., {your_app_name} - Ad Hoc)  and then select Generate.
    6. Select Download.
  7. Go back to the Certificates, Identifiers & Profiles page.
  8. Select + to create a new App ID. 
    1. Enter a description and Bundle ID, e.g., com.igloosoftware.branded.mobile.{organization_name}.share.
    2. Follow the steps on the page to finish creating a new APP ID.
  9. Go back to the Certificates, Identifiers & Profiles page.
  10. Select + to create a new In-House Provisioning Profile.
    1. In the Distribution section, select In-House and then select Continue.
    2. Select the App ID that you created in step 8 from the drop-down and then select Continue.
    3. Select your iOS Distribution Certificate and then select Continue. Use the certificate that you created in the Creating a Distribution Certificate section above. 
    4. Enter a name for the Provisioning Profile (e.g., {your_app_name} Share - In-House) and then select Generate.
    5. Select Download.
  11. Go back to the Certificates, Identifiers & Profiles page.
  12. Select + to create a new Ad Hoc Provisioning Profile.
    1. In the Distribution section, select Ad Hoc and then select Continue.
    2. Select the App ID that you created in step 8 from the drop-down and then select Continue.
    3. Select your iOS Distribution Certificate and then select Continue. Use the certificate that you created in the Creating a Distribution Certificate section above.
    4. Select the following Igloo testing devices UDIDs and then select Continue.
      • c6ba315377a9b4682bb839dda78458497d08942e
      • 8f948c292cb2932a752755d12bd936e56804baf6
    5. Enter a name for the Provisioning Profile (e.g., {your_app_name} Share - Ad Hoc)  and then select Generate.
    6. Select Download.
  13. Share the required information with the Igloo Team. An Igloo Project Manager will provide details on how to share this information.

Android distribution

Getting ready

To set up Android distribution, you require:

  • A Google Play Store account
  • Access to your organization's Google Firebase Console account

There may be a low, one-time fee to set up the account. For more information, see Google Play Console (About) and Google Play Console (Signup).

As part of setting up the application, you must provide the Igloo Team with the following: 

  • Firebase Cloud Messaging (FCM) details 

The Igloo team uses this information to set up push notifications.

Setting up Firebase Cloud Messaging (FCM)

By following the steps below, you should be able to provide the Igloo Team with:

  • google-services.json file
  • A text file containing Server Key and Legacy Key

Steps to set up FCM:

  1. Log in to Google Firebase Console.
  2. Select + Add project.
  3. Enter a project name and then select Continue.
  4. Select whether Google Analytics is enabled or disabled.
    • If you selected to enable, select Continue. Select the Google Analytics account to use, and then select Create Project.
    • If you selected to disable, select Create Project.
  5. Select your newly created project.
  6. Select the Android icon.
  7. Enter an app package name, e.g., com.igloosoftware.branded.mobile.{organization_name}.
  8. (Optional) Enter an App nickname.
  9. (Optional) Enter a debug signing certificate SHA-1.
  10. Select Register app.
  11. Select the cog next to Project Overview.
  12. Select Project settings.
  13. Select the General tab.
  14. In the Your Apps section, select the app that you just created.
  15. Select google-services.json to download the file.
  16. Select the Cloud Messaging tab.
  17. In the Project credential section, copy the Server Key and Legacy Server Key into a text file.
  18. Share the required information with the Igloo Team. An Igloo Project Manager will provide details on how to share this information.

Setting up of Accounts for Internal Testing and Validation

You must set up two user accounts in your digital workplace so that Igloo can test and support Igloo Mobile Branded Edition. These accounts should have the following attributes:

  • Account 1
    • First name: Test
    • Last name: IglooMobil1
    • Email: prem_mobile_1@igloosoftware.com
  • Account 2
    • First name: Test
    • Last name: IglooMobil2
    • Email: prem_mobile_2@igloosoftware.com

0 Comments

Sorry, comments are closed.
  • 3,287 views
  • 4 previews
  • 3 versions
  • 0 comments
  • 1 follower
     
    1 subscriber is following updates on this item.
Avg. Rating:
Updated By:
Jesse Langstaff
 
July 27, 2021
Posted By:
Jesse Langstaff
 
July 19, 2021
Versions:
v.3
Search this area
Viewed 3,287 times