Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 14008 [details]
I'm trying to make the final build to release a game for Apple TV.
When I try to make the final build, with Release, LLVM compiler and --bitcode=asmonly on mtouch parameters I get the following error:
MT5209: Native linking error: building for tvOS, but linking in object file built for iOS, file '/Users/Kak/diskd/projects/pacman/sln/tvos_pacman/tvos_game/obj/iPhone/Release/mtouch-cache/CoconutChomperTV.exe.arm64-llvm.o' for architecture arm64 (MT5209)
Compiling in debug and release (even with LLVM) works and runs on Apple TV. Problem only appears with --bitcode=asmonly
Created attachment 14009 [details]
attached system info
I've been having the same problem for two days now. Is there any news?
I have tried with every combination of settings now. Everything with --bitcode=asmonly fails and everything without it works (debug/ release and simulator/device). I can even "Archive for publishing" without "--bitcode=asmonly" and then using this option fails.
My complete details are in:
I even create an brand new single view project changing nothing (not even the base code) and it builds ok, I then put in --bitcode=asmonly and it fails. Changed nothing else.
Has ANYONE got a xamarin build into the app store? If so, what did they do?
The first reported error (MT5202) was already fixed and the missing frameworks (that needed to be added manually) is fixed by
Both fixes to be available in our next preview.
@Rod you're likely hitting the same issue - but just to be sure please open a different bug report and attach your full build logs (as described in ) and we'll do our best to give you workarounds until a new public preview is out.