Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A13C3200C92 for ; Mon, 12 Jun 2017 20:17:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9FDD0160BD9; Mon, 12 Jun 2017 18:17:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E6C5C160BCF for ; Mon, 12 Jun 2017 20:17:03 +0200 (CEST) Received: (qmail 288 invoked by uid 500); 12 Jun 2017 18:17:03 -0000 Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@cordova.apache.org Received: (qmail 276 invoked by uid 99); 12 Jun 2017 18:17:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Jun 2017 18:17:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id AB0951A0531 for ; Mon, 12 Jun 2017 18:17:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id gL-lWTWGKtuw for ; Mon, 12 Jun 2017 18:17:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 1BE9F5F2A8 for ; Mon, 12 Jun 2017 18:17:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 81197E0D54 for ; Mon, 12 Jun 2017 18:17:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1F79821E0E for ; Mon, 12 Jun 2017 18:17:00 +0000 (UTC) Date: Mon, 12 Jun 2017 18:17:00 +0000 (UTC) From: "Matthew (JIRA)" To: issues@cordova.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CB-12599) Cordova CLI - ios build release signing issues MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 12 Jun 2017 18:17:04 -0000 [ https://issues.apache.org/jira/browse/CB-12599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046849#comment-16046849 ] Matthew edited comment on CB-12599 at 6/12/17 6:16 PM: ------------------------------------------------------- I am also having an issue with this. I recently updated my signing certificates since they were about to expire and after creating new provisioning profiles (and updating build.json), I am no longer able to build. My certificates and associated private keys are in the login keychain as expected. Xcode builds dev builds and distribution builds without issues. If I remove the provisiningProfile entry from this build.json, that throws a different error until I add it back in. I've been really confused by what appears to be conflicting advice Cordova's pages about using just the string "iPhone Developer." I've also noticed that if I put the certificates I have into the System keychain, I can build from the command line (but not with jenkins). I didn't think the System keychain was the appropriate place for these certificates but it was an interesting find when I tried that. Xcode 8.3.2 I can get two different error statements based on whether I run this in jenkins or through the command line over SSH. Jenkins {noformat} Provisioning profile "xmobile dev profile" doesn't include signing certificate "iPhone Developer: Matthew Allison (EZCX646UL2)". {noformat} SSH command line {noformat} No certificate matching 'iPhone Developer: Matthew Allison' for team 'XHP8M4362G': Select a different signing certificate for CODE_SIGN_IDENTITY, a team that matches your selected certificate, or switch to automatic provisioning. Code signing is required for product type 'Application' in SDK 'iOS 10.3' {noformat} {code:java} "ios": { "debug": { "codeSignIdentity": "iPhone Developer: Matthew Allison (EZCX646UL2)", "developmentTeam": "XHP8M4362G", "packageType": "development", "provisioningProfile": "25178f0f-7562-46fa-91d4-2aa4dff903ea" } {code} was (Author: malco): I am also having an issue with this. I recently updated my signing certificates since they were about to expire and after creating new provisioning profiles (and updating build.json), I am no longer able to build. My certificates and associated private keys are in the login keychain as expected. Xcode builds dev builds and distribution builds without issues. If I remove the provisiningProfile entry from this build.json, that throws a different error until I add it back in. I've been really confused by what appears to be conflicting advice Cordova's pages about using just the string "iPhone Developer." I've also noticed that if I put the certificates I have into the System keychain, I can build from the command line (but not with jenkins). I didn't think the System keychain was the appropriate place for these certificates but it was an interesting find when I tried that. Xcode 8.3.2 {noformat} No certificate matching 'iPhone Developer: Matthew Allison' for team 'XHP8M4362G': Select a different signing certificate for CODE_SIGN_IDENTITY, a team that matches your selected certificate, or switch to automatic provisioning. Code signing is required for product type 'Application' in SDK 'iOS 10.3' {noformat} {code:java} "ios": { "debug": { "codeSignIdentity": "iPhone Developer: Matthew Allison (EZCX646UL2)", "developmentTeam": "XHP8M4362G", "packageType": "development", "provisioningProfile": "25178f0f-7562-46fa-91d4-2aa4dff903ea" } {code} > Cordova CLI - ios build release signing issues > ---------------------------------------------- > > Key: CB-12599 > URL: https://issues.apache.org/jira/browse/CB-12599 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-cli, cordova-ios > Affects Versions: 3.5.0 > Environment: Cordova @ 6.5.0 > Cordova CLI @ 6.5.0 > Cordova-ios@4.3.1 > XCode @ 8.2.1 > OS X El Capitan @ 10.11.5 > Reporter: Anton Van Zyl > Labels: build, easyfix, ios, ios-deploy, ios10 > Fix For: cordova-ios@4.4.1 > > > When Signing of the ios application with Cordova-ios@4.3.1 and XCode 8.2.1 through CLI using build.json: > {code:title=CLI Command|borderStyle=solid} > `sudo cordova build ios --release --device --buildConfig` > {code} > I get the following error: > > {quote} > No profile for 'something.something.something' were found: Xcode couldn't find a provisioning profile matching 'something.something.something'. Code signing is required for product type 'Application' in SDK 'iOS 10.2' > {quote} > > I can however do a archive through Xcode, and successfully upload the ios application to the app-store for testing. This all just tells me that my certificates and provisioning profiles are all available. Xcode can sign my app. > Is there something I am missing, doing wrong or still need to do to get cordova building ios? > build.json file part: > {code:title=build.json|borderStyle=solid} > "release" : { > "codeSignIdentity" : "iPhone Developer", > "developmentTeam" : "", > "packageType" : "app-store" > } > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org For additional commands, e-mail: issues-help@cordova.apache.org