cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse <>
Subject Re: Xcode 8 packaging changes
Date Fri, 16 Sep 2016 00:31:16 GMT
+1 to dropping 6 and moving towards 8
What is apple's required version of xcode for submitting apps to the app

Does it make sense to always build with the developer cert unless the dev
specified otherwise?  I think there might be cases where I would want to
run the release build on my own device before submitting it.


On Thu, Sep 15, 2016 at 1:38 PM, Darryl Pogue <> wrote:

> So Xcode 8 is out, and it simplifies some aspects of code signing, but
> complicates the process of packaging an app.
> Currently, cordova-ios will use the "iPhone Developer" certificate when
> building a debug build, and the "iPhone Distribution" certificate when
> making a release build. It uses xcrun with the (deprecated)
> PackageApplication option to bundle up the build into an IPA file.
> Xcode 8 has automatic provisioning, which means instead of dealing with
> specifying a bunch of certificate files, you can pretty much just give it a
> team identifier and it will figure things out. With one catch: you need to
> use the "iPhone Developer" certificate. Support for the team identifier in
> build.json has already been added to cordova-ios master.
> However, in order to make a build in Xcode 8 with automatic provisioning
> and a distribution certificate, you need to run the xcodebuild archive
> step, and then an exportArchive step to generate the IPA. This workflow has
> been supported since Xcode 7.
> Currently, since Cordova uses xcrun PackageApplication, it is packaging up
> a release build with the development certificate. This build cannot be
> submitted to the App Store.
> My proposal is for cordova-ios to drop support for Xcode 6 with the xcrun
> packaging, and start using xcodebuild for archiving and generating the IPA.
> I suppose that would have to wait for a major version bump of cordova-ios,
> unless we detected the Xcode version and kept the old code around
> conditionally.
> As part of packaging, we would need to generate a exportOptions.plist file,
> indicating what type of build to package (development, enterprise, ad-hoc,
> or app-store). I'd suggest we add a "packageType" or "buildType" field to
> build.json for specifying this value (with a default of development).
> I'm happy to start prototyping this on a branch if it sounds like the right
> approach going forward.
> Related info:
> #building-for-distribution-xcode-8

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message