You will need to change some things in your ist file that differ from your development configuration. Make sure you're working on a clean and fresh working directory with the latest sources of your project (and maybe a specific branch). Step 2: Make A Clean Checkout Of Your Sources Otherwise you would always have to create a new certificat when setting up a new computer. Remember the password of that file, so you can import the certificate on any machine you need in the future. When you've created a new certificate by the guidance of the Apple Website, don't only download it to your machine, but directly export the private key as a *.p12 file afterwards from the Keychain Access tool. If you've everything prepared, install the certificate (by double-clicking the *.p12) and the provisioning profile (likewise by double-clicking). Yes, you need to do that – but hopefully the last time for a long, long time. Step 1: Set Up The Certificate And The Provisioning Profile I prefer it that way, but I won't go into any product specific details here because that would go beyond the scope of this post. The latter needs to run with an account that runs on the business plan, as you you need the "business feature" of headless builds to run all the stuff from the command line.Įverything described below can easily be run via simple shell scripts, but if you're running a fully featured build server like TeamCity or Jenkins anyway, go for it. You need to install Xcode and its Command Line Tools, as well as Xamarin. I highly recommend you to use a dedicated machine. Obviously everything has to be executed on a Mac, so it won't work on your average Windows box or on a Linux server. The Process Of Automatic Distribution Prerequisites: A Build Server With Xcode And Xamarin So setting up a new development machine once in a while can drive you crazy, and so can taking over the distribution task from a colleague who's normally doing this job but is not available at your important deadline. I think it's fair to say that those steps are hard to remember if you're not doing it every week, and it evidentially is error-prone. From there: Publish your app to your testers via TestFlight or submit it to the review process of Apple.Upload your app (.ipa) with the Application Loader desktop application to iTunes connect.Export your app (.ipa) from the Xcode Organizer.Create an iTunes Connect entry for your app (via their website).Build your Xamarin app with Xamarin Studio or Visual Studio with the "AppStore | iPhone" build configuration and archive it.Install both the certificate and the provisioning profile on your development machine.Create a distribution provisioning profile.Shipping a Xamarin iOS app to Apple follows usually those manual steps: The Manual Way Of Distributing An iOS App I can't free you from that kind of experience, but here's a way that allows you to only go through it once. That awful feeling when dealing with provisioning profiles, development and distribution certificates. Automate All The Things: Distributing Xamarin iOS Apps To The AppStore And TestFlight Without PainĮveryone who has already built and shipped an iOS app to the AppStore knows the pain.
0 Comments
Leave a Reply. |