[
https://issues.apache.org/jira/browse/CB-11860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533360#comment-15533360
]
ASF GitHub Bot commented on CB-11860:
-------------------------------------
Github user dpogue commented on the issue:
https://github.com/apache/cordova-ios/pull/257
The only reasons to go through the archive step is to ensure that the build
is signed with the right certificates. Building and deploying the .app directly
would be signed with a development certificate instead of a distribution one.
> Cordova-iOS cannot package distributions apps with Xcode 8
> ----------------------------------------------------------
>
> Key: CB-11860
> URL: https://issues.apache.org/jira/browse/CB-11860
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Affects Versions: 4.3.0
> Reporter: Darryl Pogue
> Assignee: Darryl Pogue
>
> See mailing list thread:
> https://lists.apache.org/thread.html/85a715681471c774821d76a90ec288943eca1a4bb0a267ba299d2eb3@%3Cdev.cordova.apache.org%3E
> {quote}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).{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
