Appcenter-cli: Error: Failed to analyze MachO file: Unknown load command: 2147483700
appcenter fails with:
Error: Failed to analyze MachO file: Unknown load command: 2147483700
This is server-side analysis I'm quite sure, but you'll start seeing issues about it if people attempt to upload to Test with Xcode 12.2 as the build system.
The XCUITest frameworks and libraries contain an ARM64e slice and two new Load Commands. 0x33 and 0x34
Workaround - remove the arm64e slices from the XCUITest frameworks and dylibs in the Runner.
palmerc
All 5 comments
@palmerc This is very useful info but exactly how does one perform the workaround?
snoozemoose
on 4 Dec 2020
@snoozemoose you can remove the arm64e slice easily enough with the lipo tool which will bypass the load command check. However, AppCenter still has some other problems with Test Runner's compiled in Xcode 12. So... the work around is to compile your test runner with Xcode 11, then copy the *-Runner.app and your Xcode 12 compiled app into a folder and upload the pair. It is not ideal, but does work for us.
I've been in touch with AppCenter support and they are working on the issue.
palmerc
on 4 Dec 2020
@palmerc Thank you, I'll give this a try!
snoozemoose
on 4 Dec 2020
Facing the same issue, Is this fixed now?
JayakumarKnila
on 29 Dec 2020
When is there an update to this?
timroeringDB
on 18 Jan 2021
Related issues
mamcx
路
6Comments
phantrungphat
路
3Comments
ivanmoskalev
路
3Comments
nandafirmans
路
4Comments
MicrosoftCSA
路
4Comments
Most helpful comment
@snoozemoose you can remove the arm64e slice easily enough with the lipo tool which will bypass the load command check. However, AppCenter still has some other problems with Test Runner's compiled in Xcode 12. So... the work around is to compile your test runner with Xcode 11, then copy the *-Runner.app and your Xcode 12 compiled app into a folder and upload the pair. It is not ideal, but does work for us.
I've been in touch with AppCenter support and they are working on the issue.