As it turns out xcodebuild logs the actual error somewhere before and just gives the summary at the end. The error building the archive was a library that didn't have bitcode enabled.
Oh well. Still would love to understand why "build" adds the " libswiftRemoteMirror.dylib" though. On Sun, Sep 25, 2016 at 12:07 PM, Torsten Curdt <tcu...@vafer.org> wrote: > Current reading suggests that (whatever ibswiftRemoteMirror.dylib is) > this is a difference between xcodebuild archive vs build (for whatever > reasons). Since I can't find any further information on this I tried the > archive approach: > > xcodebuild > -project "Foo.xcodeproj" > -scheme "App" > -configuration "Release" > -sdk "iphoneos10.0" > -archivePath "/foo/build/iphoneos10.0/Release.xcarchive" > archive > PROVISIONING_PROFILE="48d27476-3d52-45a5-9a56-798dc440f66a" > CODE_SIGN_IDENTITY="iPhone Distribution: Foo (L9EV9UUBV1)" > > unfortunately that fails with very little information > > ** ARCHIVE FAILED ** > > The following build commands failed: > Ld /Users/tcurdt/Library/Developer/Xcode/DerivedData/Foo- > btjldebpjrkpqcgbdqvakwjpfyim/Build/Intermediates/ArchiveIntermediates/App/ > IntermediateBuildFilesPath/Foo.build/Release-iphoneos/ > Foo.build/Objects-normal/armv7/Foo normal armv7 > (1 failure) > > Looking at the target for "Ld" I find > > ls -la /Users/tcurdt/Library/Developer/Xcode/DerivedData/Foo- > btjldebpjrkpqcgbdqvakwjpfyim/Build/Intermediates/ArchiveIntermediates/App/ > IntermediateBuildFilesPath/Foo.build/Release-iphoneos/ > Foo.build/Objects-normal/armv7/Foo* > > -rw-r--r-- 1 tcurdt staff 136881 Sep 25 11:48 > [...]/Foo.build/Objects-normal/armv7/Foo-OutputFileMap.json > -rw-r--r-- 1 tcurdt staff 26533 Sep 25 11:48 > [...]/Foo.build/Objects-normal/armv7/Foo-Swift.h > -rw-r--r-- 1 tcurdt staff 8672 Sep 25 11:48 > [...]/Foo.build/Objects-normal/armv7/Foo-master.swiftdeps > -rw-r--r-- 1 tcurdt staff 18599 Sep 25 11:48 > [...]/Foo.build/Objects-normal/armv7/Foo.LinkFileList > -rw-r--r-- 1 tcurdt staff 608 Sep 25 11:48 > [...]/Foo.build/Objects-normal/armv7/Foo.swiftdoc > -rw-r--r-- 1 tcurdt staff 521816 Sep 25 11:48 > [...]/Foo.build/Objects-normal/armv7/Foo.swiftmodule > -rw-r--r-- 1 tcurdt staff 68757 Sep 25 11:48 > [...]/Foo.build/Objects-normal/armv7/Foo_dependency_info.dat > > Any idea? > > cheers, > Torsten > > > On Sun, Sep 25, 2016 at 2:02 AM, Torsten Curdt <tcu...@vafer.org> wrote: > >> I was just trying to upload an IPA to Testflight I am getting: >> >> ERROR ITMS-90171: "Invalid Bundle Structure - The binary file >> 'Foo.app/libswiftRemoteMirror.dylib' is not permitted. Your app can’t >> contain standalone executables or libraries, other than the >> CFBundleExecutable of supported bundles. Refer to the Bundle Programming >> Guide at https://developer.apple.com/go/?id=bundle-structure for >> information on the iOS app bundle structure." >> >> What's libswiftRemoteMirror.dylib? And where is it coming from? >> >> Google and SO were not particularly helpful yet. >> Any pointers would be great. >> >> cheers, >> Torsten >> > > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
