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.
Which version of Xcode are you using ?
The easiest way to get exact version information is to use the "Xamarin Studio" menu, "About Xamarin Studio" item, "Show Details" button and copy/paste the version informations (you can use the "Copy Information" button).
=== Xamarin Studio ===
Version 4.0.12 (build 3)
Installation UUID: 242b7503-605e-4f20-8e19-839fff7f3c03
Mono 3.2.0 ((no/7c7fcc7)
Package version: 302000000
=== Xamarin.Android ===
=== Apple Developer Tools ===
Xcode 4.2 (828)
=== Xamarin.iOS ===
Version: 220.127.116.11 (Starter Edition)
Build date: 2013-10-09 11:14:45-0400
=== Xamarin.Mac ===
Xamarin.Mac: Not Installed
=== Build Information ===
Release ID: 400120003
Git revision: 593d7acb1cb78ceeeb482d5133cf1fe514467e39
Build date: 2013-08-07 20:30:53+0000
Xamarin addins: 25a0858b281923e666b09259ad4746b774e0a873
=== Operating System ===
Mac OS X 10.7.5
Darwin Bilgins-MacBook-Air.local 11.4.2 Darwin Kernel Version 11.4.2
Thu Aug 23 16:25:48 PDT 2012
Xcode 4.2 is pretty old (you might want to upgrade). Also note that you're targetting 6.0 with the 5.0 SDK. That's possible but some new API won't work (e.g. in new 6.0 frameworks).
Anyhow the issue is that newer versions of Xcode include a more recent `dsymutil` with the `-z` option:
When used when creating a dSYM file, this option will suppress the
emission of the .debug_inlines, .debug_pubnames, and .debug_pubtypes
sections since dsymutil currently has better equivalents: .apple_names
and .apple_types. When used in conjunction with --update option, this
option will cause redundant accelerator tables to be removed.
With Xcode 4.2 you can workaround this by adding:
to your project options (IOS Build, Additional mtouch arguments). That will turn off the .dSYM generation.
You can tell produce them manually (e.g. before releasing) with the same command as above (bu without the `-z` option). E.g.
-t 4 -o
With Xamarin.iOS 7.0 we require at least Xcode 4.4.