iOS Provisioning Profile Renewal Process with MDM

  • strict warning: Only variables should be passed by reference in /var/sites/e/ on line 61.
  • strict warning: Only variables should be passed by reference in /var/sites/e/ on line 61.
  • strict warning: Declaration of views_handler_field_user_name::init() should be compatible with views_handler_field_user::init(&$view, $data) in /var/sites/e/ on line 61.
kolin.augie's picture


Joined: Dec 12, 2014
Your rating: None (1 vote)

Hello all! We have what appears to be a common scenario, but have yet found the best answer.

We will be approaching the time to renew our iOS Distribution provisioning profiles for internal apps in the next few months. These apps are managed and deployed through MDM. I have tested the process of uploading a renewed profile through our MDM. The updated profile is displayed and the Renewal Date now matches the expiration date of the new profile.

My concern is relying on an MDM to update the profiles for all devices. The other option appears to be to re-package the current apps with the renewed profile and deploy the build again through MDM.

Any recommendations or best practices for this scenario?

I should note that all iOS devices are supervised and shared devices.

Thank you in advance!

jafuller's picture


Joined: Aug 28, 2012

Update the App

Your rating: None (1 vote)

I would recommend updating the build of your app and deploying it that way. It would allow you to better manage the deployment and force updates down to the device. I've found this to be more stable than profile updates. Just an opinion though. I'm sure others have theirs.

James Fuller
senior systems engineer

James Fuller | Starbucks


Who is online?

There are currently 0 admins, 0 users and 158 guests online. Connected users: .

Recent Activity