Jenny Gee created CB-8380:
-----------------------------

             Summary: Running 'cordova build --release --device' fails
                 Key: CB-8380
                 URL: https://issues.apache.org/jira/browse/CB-8380
             Project: Apache Cordova
          Issue Type: Bug
          Components: CLI, iOS
    Affects Versions: 3.8.0
            Reporter: Jenny Gee


When running 'cordova build --release --device', it fails with the following 
error:

{code}
Check dependencies

Code Sign error: No code signing identities found: No valid signing identities 
(i.e. certificate and private key pair) matching the team ID “(null)” were 
found.

warning: no rule to process file 
'/Users/gfxbbuser/TestProjects/iosTestXCode6/platforms/ios/iosTestXCode6/main.m'
 of type sourcecode.c.objc for architecture armv7 armv7s arm64

warning: no rule to process file 
'/Users/gfxbbuser/TestProjects/iosTestXCode6/platforms/ios/iosTestXCode6/Classes/AppDelegate.m'
 of type sourcecode.c.objc for architecture armv7 armv7s arm64

warning: no rule to process file 
'/Users/gfxbbuser/TestProjects/iosTestXCode6/platforms/ios/iosTestXCode6/Classes/MainViewController.m'
 of type sourcecode.c.objc for architecture armv7 armv7s arm64

CodeSign error: code signing is required for product type 'Application' in SDK 
'iOS 8.1'

** BUILD FAILED **
{code}


Environment found:
============

- Yosemite
- XCode6.1
- Certificates and Provisioning Profiles are all installed

First Build in Cordova 3.5.0
- No Problems. And app is signed

Then build in Cordova 4.2.0
- Error is above

Then built in Cordova 4.2.1-dev
- Same error above

In all cases, all I did was switch the version of cordova, and it's quite 
apparent to me that it can't find the proper signing identity. 

oh yes - In both the above cases, I even had an iPhone attached, just for kicks.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to