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.
I am facing size limit exceeded error for Xamarin Apple watch App while uploading to TestFlight .
I removed Newtonsoft from watch application still App size is 55.1 MB.
I am using System and System.Core references only and have 1-2 MB resources (image and audio).
Please let me know the solution for the same.
You get large binaries for watchOS partly because we need to generate bitcode (and that's large).
To be able to help you find ways to further reduce the size of the final binary we would need at least your full verbose build output.
To get full build logs just set the log verbosity to diagnostic at the following locations:
- On Visual Studio for Mac: Preferences > Projects > Build
- On Visual Studio for Windows: Tools > Options > Projects and Solutions > Build and Run
Also please provide you version information.
Easiest way to get exact version information:
- On Visual Studio for Mac: "Visual Studio" menu, "About Visual Studio" item, "Show Details" button.
- On Visual Studio for Windows: "Help menu", "About Microsoft Visual Studio" item.
Then copy/paste the version information (you can use the "Copy Information" button).
I would also always recommend using Stack Overflow  or the Xamarin Forums  for that kind of question because the broader developer community is fast to respond and can provide helpful tips and tricks (;
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!