Can not build my project in AppCode 2016.2 EAP


I still can build it in Xcode. It also worked fine in AppCode 2016.1.3. However, in 2016.2 it failed with:

"Error:linker command failed with exit code 1 (use -v to see invocation)"

Problem seems to be CocoaPod/My Project Test Target:

My Podfile looks basically like this 

source ''
platform :ios, '8.0'

project "qeep"

target :qeep do
pod 'AFNetworking'
# some more pods ...

target :qeepTests do
inherit! :search_paths
pod 'OCMock', '~> 3.2.2'






Hi Stefan.

Could you please attach build log (Messages tool window | Show Build Log)? Also please specify which Xcode is used by AppCode (AppCode | Preferences | Tools | Xcode)?
If possible, try to isolate this in a sample project and attach to the issue.


Also please check that you’ve opened .xcworkspace instead of .xcodeproj.


Hmm, I still can not attach any file to a post in the forum. The log is really huge...

I will post the tail here:

AppCode2016.2/DerivedData/qeep-hjocmvcmrycqgwgtxhkiezbgkjtk/Build/Products/Debug-iphoneos/ -Xlinker -no_deduplicate -ObjC -lGGLAnalytics -lGGLCore -lGSDK_Overload_external -lGTMSessionFetcher_core_external -lGTMSessionFetcher_full_external -lGTMStackTrace_external -lGTM_AddressBook_external -lGTM_DebugUtils_external -lGTM_GTMURLBuilder_external -lGTM_KVO_external -lGTM_NSData+zlib -lGTM_NSDictionary+URLArguments_external -lGTM_NSScannerJSON_external -lGTM_NSStringHTML_external -lGTM_NSStringXML_external -lGTM_Regex_external -lGTM_RoundedRectPath_external -lGTM_StringEncoding_external -lGTM_SystemVersion_external -lGTM_UIFont+LineHeight_external -lGTM_core_external -lGTM_iPhone_external -lGoogleAnalytics -lProtocolBuffers_external -lsqlite3 -lstdc++ -lz -framework AVFoundation -framework AddressBook -framework AssetsLibrary -framework AudioToolbox -framework CoreData -framework CoreFoundation -framework CoreGraphics -framework CoreLocation -framework CoreMedia -framework CoreMotion -framework CoreTelephony -framework EventKit -framework EventKitUI -framework GoogleMobileAds -framework MediaPlayer -framework MessageUI -framework OCMock -framework Security -framework StoreKit -framework SystemConfiguration -weak_framework AdSupport -framework XCTest -fobjc-arc -fobjc-link-runtime -L/Applications/ -Xlinker -add_ast_path -Xlinker /Users/skerkewitz/Library/Caches/AppCode2016.2/DerivedData/qeep-hjocmvcmrycqgwgtxhkiezbgkjtk/Build/Intermediates/ -framework Pods_qeepTests -framework Pods_qeep_qeepTests -Xlinker -dependency_info -Xlinker /Users/skerkewitz/Library/Caches/AppCode2016.2/DerivedData/qeep-hjocmvcmrycqgwgtxhkiezbgkjtk/Build/Intermediates/ -o /Users/skerkewitz/Library/Caches/AppCode2016.2/DerivedData/qeep-hjocmvcmrycqgwgtxhkiezbgkjtk/Build/Intermediates/
ld: framework not found Pods_qeep_qeepTests
clang: error: linker command failed with exit code 1 (use -v to see invocation)


The following build commands failed:
Ld /Users/skerkewitz/Library/Caches/AppCode2016.2/DerivedData/qeep-hjocmvcmrycqgwgtxhkiezbgkjtk/Build/Intermediates/ normal arm64
Ld /Users/skerkewitz/Library/Caches/AppCode2016.2/DerivedData/qeep-hjocmvcmrycqgwgtxhkiezbgkjtk/Build/Intermediates/ normal armv7
(2 failures)


The line parameter "-framework Pods_qeepTests -framework Pods_qeep_qeepTests" looks suspicious to me: i would say "Pods_qeepTests" is correct, "Pods_qeep_qeepTests" looks bogus to me.

I will try to reproduce the issue an in test project.


AppCode 2016.2 EAP
Build #OC-162.646.13, built on June 1, 2016
AppCode EAP User
Expiration date: July 1, 2016
JRE: 1.8.0_76-release-b205 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o

Running on OSX 10.11.5 and using Xcode 7.3.1 (7D1014)



Oh, I just realised I the mail for this thread ended up in my spam folder. My bad, sorry about that.

However, I did try to create a test project and reproduce the issue - of course everything compiles fine.

So this is the third time I have an issue neither you guy can confirm nor I can reproduce in a test project and therefore I really start to wonder if there is a problem in my Xcode project file.

Anyways, I guess you guys can ignore this issue as long as nobody else complain about a similar issue.



Please sign in to leave a comment.