When attempting to build my Swift 4 project in Xcode 9 beta 2, some code signing error occurs after which the build of my app is discontinued.
The error that is shown in Xcode:
/usr/bin/codesign --force --sign - --preserve-metadata=identifier,entitlements '/Users/nickgaens/Library/Developer/Xcode/DerivedData/Emprova_Swift-bbvmoytlhlbqpueyftstselvwhdj/Build/Products/Debug-iphonesimulator/Emprova GPS Swift.app/Frameworks/Alamofire.framework'
/Users/nickgaens/Library/Developer/Xcode/DerivedData/Emprova_Swift-bbvmoytlhlbqpueyftstselvwhdj/Build/Products/Debug-iphonesimulator/Emprova GPS Swift.app/Frameworks/Alamofire.framework: No such file or directory
As you might notice, the --sign
argument is followed by a single -
character.
My setup:
platform :ios, '10.0'
target 'Emprova GPS Demo Swift' do
use_frameworks!
pod 'Alamofire', '~> 4.5.0'
pod 'AlamofireNetworkActivityIndicator', '~> 2.2.0'
pod 'KeyClip'
pod 'Localize-Swift', '~> 1.7.1'
pod 'FMDB'
end
target 'Emprova GPS Swift' do
use_frameworks!
pod 'Alamofire', '~> 4.5.0'
pod 'AlamofireNetworkActivityIndicator', '~> 2.2.0'
pod 'KeyClip'
pod 'Localize-Swift', '~> 1.7.1'
pod 'FMDB'
end
Pods.xcodeproj
to check and double check Build Settings
- Code Signing Identitiy
of the Alamofire pod/target, but it is set to Don't Code Sign
.Apple Worldwide Developer Relations Certification Authority
wasn't expired (it isn't) and is marked as trusted (it is).~/Library/Developer/Xcode/DerivedData
) and performed a Clean
(both via Cmd+K
and Cmd+Alt+Shift+K
to no avail.Preferences
- Locations
- Command Line Tools
) to both Xcode 8.3.3 (8E3004b)
and Xcode 9.0 (9M137d)
to no avail.Completely ran out of ideas after having spent multiple hours searching for a solution. Does anyone have a clue why Xcode 9 no longer builds my project?
Also, link to my issue on Alamofires GitHub page, for the sake of completeness: #2183.
The Podfile is a specification that describes the dependencies of the targets of one or more Xcode projects. The file should simply be named Podfile .
I found out what's wrong! Xcode continued using the .xcodeproj
file to open my project when selecting it on the welcome screen, but Cocoapods
requires the .xcworkspace
file to be used! There's a visual distinction between both entries on Xcode's Welcome screen afterwards: difference between Xcode workspace and project on Welcome screen.
Opening the workspace shows two projects in Xcode's Project Navigator
: one for my app and a second one named Pods
, which embodies all installed pods. Building the app no longer shows weird build errors.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With