Provisioning Profile

App Release to the MobileIron Enterprise App Store in 6 Easy Steps

We’re proud to partner with MobileIron to facilitate quicker, safer, and more reliable enterprise app deployment. Here’s a video to show you how simple your app release process can be with incapptic Connect.

Step 1: Login to your incapptic Connect account. This will bring you to your apps list, where you have an enterprise level overview of all app projects within your business

Step 2: Navigate to the app you’d like to update.

Step 3: Press ‘new version’ to upload your .ipa file and follow the instructions to upload any new metadata assets.

Step 4: Wait for incapptic Connect to handle the app signing process, as well as generate your new provisioning profile.

Step 5: Publish your new version to your MobileIron enterprise App Store

Step 6 (optional): Update labels and categories

Step Seven: Done!

App release to the Apple App Store in 6 Easy Steps

We’re huge Apple fans here at incapptic Connect (our Founder is an OG Apple Fan, and worked with them for 7 years!). iOS is the second most widely used operating system globally after Android. Because of Apple’s heightened approach to security, publishing enterprise apps to the Apple App Store can present some unique challenges that we circumvent with the incapptic Connect solution. Here’s a quick video demo.

Step 1: Login to your incapptic Connect account

Step 2: Navigate to the app you want to update, or select ‘new app’

Step 3: Upload your .ipa file

Step 4: Update your metadata & graphic assets before submitting

Step 5: Get a cup of coffee while we handle the sticky business generating a new provisioning profile and signing the app

Step 6: Upload to iTunes Connect

Step 7: Prepare your app for submission to the App Store as normal

Learn more-01.png

4 Ways to Prevent iOS Provisioning Profile Expiration

4 Ways to Prevent iOS Provisioning Profile Expiration

iOS provisioning profiles for in-house apps are only valid for 12 months. Their respective distribution certificates are valid for 36 months. The clock starts ticking the moment you generate either of them in the Apple Developer Center. Once the expiration date is reached, your app stops working. This is bad, as in-house app use cases are maturing from convenience (remember the Genentech Get-A-Room video?) to business critical.