[ 
https://issues.apache.org/jira/browse/CB-11860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15534442#comment-15534442
 ] 

ASF GitHub Bot commented on CB-11860:
-------------------------------------

Github user shazron commented on the issue:

    https://github.com/apache/cordova-ios/pull/257
  
    @dpogue Just tested this. We need to add a warning if users are not using 
the system ruby, like the  pre-reqs check for xcodebuild (it wouldn't work like 
you said without the system ruby). I didn't even need to use the 
`--developmentTeam` flag for it to work. `cordova build --device` worked like 
it did before.
    
    @chancezeus in `platforms\ios\device` there is already a symlink to the 
.app bundle. Unfortunately `ios-deploy` doesn't traverse the symlink for some 
reason, gives an error : `Can't access app path 
'/Users/shaz/Desktop/f/platforms/ios/build/device/my.app' : No such file or 
directory` . I'll have to make a patch release to ios-deploy for this, and 
update the minimum requirements to cordova-ios that has to go with this pull 
request.


> 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

Reply via email to