I'm getting a warning that The provisioning profile "iOSTeam Provisioning Profile: *" is expiring soon. I'm not sure what to do and the Apple documentation, even the Quick Start Guide, is overwhelming and confusing for me.

Some developers say "Just wait until it expires, Xcode will then offer to fix it.", others like Jared Sinclair adamantly oppose doing that. I'd do what he suggests, but I'm not sure how and would likely mess up stuff.

Is there a truly user friendly guide on how to handle iOS Certificates and Provisioning Profiles?

  • 2
    Exactly this. You are most certainly not alone. They tell you what to do but any starting point seems arbitrary. +1. – chiggsy Apr 5 '16 at 4:22
  • I think you need to divide and conquer. Your question does contain an issue that could stand on its own as a question, but instead this question is mostly about your discontentment and not really a question anybody can answer. – medbot Apr 5 '16 at 23:46

It's hard to know what specific step you're stumped on - since an error signing development builds will cascade and cause issues when you upload. Uploading can have new issues if you don't have problems running development builds.

The outline I use is:

It breaks down the steps to code signing which also deals with profiles. I'll assume you are set up with a proper app / bundle ID in iTunes connect. If that needs guidance, you can refer to this diagram from https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/Introduction/Introduction.html

enter image description here

The green boxes are the iTunes Connect portions you need to accomplish in the web app or iTunes Connect iOS app.

If the full process is too much, just focus on breaking up the process into smaller chunks or try reviewing the quick start guide.

Worst case, if you don't have the time to work through things - you could see about partnering with another developer or paying someone to help you set things up. If you want to focus on the coding - outsourcing the management to someone that's already done the learning and has a handful of apps through all the steps can probably save you time struggling with things that don't in the end make a better app but help you navigate the systems for submitting apps.

  • Thank you for the effort you put into this, really appreciate it. Unfortunately, I've come to the conclusion that the Apple documentation is basically unusable. For example, the App Distribution Workflow is one of the worst. Right away it starts out with "To learn how to", then lists a truckload of stuff, some with duplicate "resolutions." This is exactly how not to write documentation. The more options one has, the less likely one will be confident that the choice is the optimum one. The Quick Start Guide starts off promising, but then in one or two "Next" clicks falls into the same pattern. – Yimin Rong Apr 5 '16 at 10:44
  • Also - don't forget that tech is really about overcoming the struggles everyone has with code, change and documentation or lack thereof. You're not wrong about it being hard @YiminRong – bmike Apr 5 '16 at 16:25

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .