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
As for going with "build" instead of "archive" I see this in the log
builtin-swiftStdLibTool --copy --verbose --sign
99D83694482D58B0EBB9A85D9528ECC7247A7DB1
--scan-executable /project/build/iphoneos10.0/Applications/Foo.app/Foo
--scan-folder
/project/build/iphoneos10.0/Applications/Fo
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"
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. Re
