Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linting a swift iOS pod raises code sign errors without a certificate #13

Closed
kylef opened this issue Dec 17, 2014 · 3 comments · Fixed by CocoaPods/CocoaPods#3083
Closed
Labels

Comments

@kylef
Copy link

kylef commented Dec 17, 2014

Is it possible to not code sign when linting? Otherwise it will be difficult listing Swift iOS pods on travis etc where we don't have a certificate.

$ bundle exec pod lib lint URITemplate.podspec

 -> URITemplate (0.1.0)
    - WARN  | The URL (https://github.com/kylef/URITemplate.swift) is not reachable.
    - ERROR |  [BEROR]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.
    - ERROR |  [BEROR]CodeSign error: code signing is required for product type 'Framework' in SDK 'iOS 8.1'
    - ERROR | [iOS]  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.
    - ERROR | [iOS]  CodeSign error: code signing is required for product type 'Framework' in SDK 'iOS 8.1'

[!] URITemplate did not pass validation.
You can use the `--no-clean` option to inspect any issue.
@kylef kylef added the question label Dec 17, 2014
@mrackwitz
Copy link
Member

Code Signing is required for Cocoa Touch Frameworks, otherwise the xcodebuild for the generated framework target won't succeed, at least that's my last info.

@neonichu
Copy link
Member

It is required when building for the device, but not when building for the simulator.

@segiddins
Copy link
Member

So linting should specifically build against a simulator architecture for iOS?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants